Opened 9 years ago
Closed 8 years ago
#1033 closed defect (fixed)
eassylogging prints message in console in stead of log file
| Reported by: | George Merticariu | Owned by: | Vlad Zamfir |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | undecided | Version: | development |
| Keywords: | Cc: | Dimitar Misev, Peter Baumann | |
| Complexity: | Medium |
Description
- Create an empty collection
- ./rasql -q 'select avg_cells(test - test/2 -test/3) from test' —out string
./rasql: rasdaman query tool v1.0, rasdaman v9.1.0-g7f0bf32 — generated on 22.10.2015 18:28:43.
opening database RASBASE at localhost:7001...ok
Executing retrieval query…23/10/2015 13:09:06.778 [ERROR] Internal error: RasnetClientComm::executeQuery(): illegal status value 2
ok
Query result collection has 0 element(s):
./rasql done.
The message shouldn't be printed in console as error. It looks like a log line for the log file.
Note: Status 2 shouldn't be logged as error since it represents empty result.
Change History (3)
comment:2 by , 9 years ago
According to the code on the sever side, status 2 means empty result. Why is it treated in rnp as error?
comment:3 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
It's an error in the client side of rasnet, and rasql doesn't have a log file. So the correct fix is to remove the invalid log message altogether?