Opened 5 months ago

Last modified 4 months ago

#1546 new defect

rasserver log error reporting not always informative

Reported by: bbell Owned by:
Priority: major Milestone: 9.5
Component: rasserver Version: development
Keywords: Cc: bphamhuu, dmisev
Complexity: Easy


when running this query from the terminal:

$ rasql -q 'select csv(arcsin(100f))' --out string
rasql: rasdaman query tool v1.0, rasdaman 9.4.0.
opening database RASBASE at localhost:7001...ok
Executing retrieval query...rasdaman error 510: Execution error 510 in line 1, column 12, near token arcsin: The argument is outside the function domain.
aborting transaction...ok
rasql done.

the error reporting is fine; however, when checking the rasserver log output, we only see:

Error number: 510 Token: arcsin Line: 1 Column: 12

Similar errors are logged for other operations (e.g. pow and arccos).

This is a problem because petascope users do not see the query-time error messages, and instead use the rasserver log to get a better handle on the problem.

Setting the ostream to the rasserver.log to also parse the error messages would improve the user-experience.

Change History (1)

comment:1 Changed 4 months ago by dmisev

  • Component changed from undecided to rasserver
  • Milestone set to 9.5
Note: See TracTickets for help on using tickets.