Opened 9 years ago
Last modified 8 years ago
#1230 closed defect
Rasql_Error when scale axis to a slicing point — at Version 4
Reported by: | Bang Pham Huu | Owned by: | Dimitar Misev |
---|---|---|---|
Priority: | minor | Milestone: | 10.0 |
Component: | petascope | Version: | development |
Keywords: | WCPS 2.0, error in scale, scale slicing point | Cc: | Dimitar Misev, Alex Dumitru, Vlad Merticariu |
Complexity: | Medium |
Description (last modified by )
scaling to an interval that contains any slices should throw an error in rasql.
Examples:
SELECT encode(SCALE(c, [100,243]), "csv" ) FROM rgb AS c
and
SELECT encode(SCALE(c, [100:102,243]), "csv" ) FROM rgb AS c
and
SELECT encode(SCALE(c, [100,100:243]), "csv" ) FROM rgb AS c
In all of these cases rasql should throw an exception: "Invalid scaling minterval".
Scaling in rasdaman is handled in source:qlparser/qtbinaryfunc.cc (QtScale class).
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Component: | undecided → rasql |
---|---|
Owner: | set to |
Status: | new → assigned |
Summary: | WCPS1.5_Error when scale axis to a slicing point → Rasql_Error when scale axis to a slicing point |
Dimitar, I think in this case, Rasql should throw an exception when scale at a point, instead of error like this.
rasql -q "select csv(scale( c, [100,243] )) from rgb AS c " --out string rasql: rasdaman query tool v1.0, rasdaman v9.2.0-beta1-gf79e291 -- generated on 21.01.2016 14:39:26. opening database RASBASE at localhost:7001...ok Executing retrieval query...rasdaman error 0: General error received from the server. aborting transaction...E0209 09:11:56.585736960 12746 tcp_client_posix.c:171] failed to connect to 'ipv4:10.70.11.237:7002': socket error: connection refused E0209 09:11:57.586939956 12746 tcp_client_posix.c:171] failed to connect to 'ipv4:10.70.11.237:7002': socket error: connection refused E0209 09:11:59.050714220 12746 tcp_client_posix.c:171]
comment:3 by , 9 years ago
Priority: | major → minor |
---|
comment:4 by , 9 years ago
Description: | modified (diff) |
---|
Note:
See TracTickets
for help on using tickets.
Please check if scaling to a point is valid in the WCPS standard, perhaps an interval is mandatory.