#2344 closed defect (fixed)
rasql - cannot update an empty collection with negative bounds
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 10.0 |
Component: | rasserver | Version: | 9.8 |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
Complexity: | Medium |
Description
Input 2D tiff file has size:
Files: /home/rasdaman/tmp/test_eu_dem_parsec/EU_DEM_32_3035.tiff Size is 8821, 6770
Create test collection:
CREATE COLLECTION EU_DEM_32 FloatSet INSERT INTO EU_DEM_32 VALUES <[0:0,0:0] 0f> TILING ALIGNED [0:*,0:*] tile size 4194304
With this update with negative bound, it returns error:
'UPDATE EU_DEM_32 SET EU_DEM_32[0:8820,-3020:3749] ASSIGN decode(<[0:0] 1c>, "GDAL", "{\"filePaths\":[\"/home/rasdaman/tmp/test_eu_dem_parsec/EU_DEM_32_3035.tiff\"]}")'... parsing... checking semantics... evaluating... [ERROR] - 2020-08-03 11:00:14,175, qlparser/qtupdate.cc:541: source domain [0:8820,0:6769] isn't within the target domain [0:8820,-3020:3749] rasdaman error 967: Update error 967 in line 1, column 1, near token UPDATE: Source MDD domain is not within target update MDD domain.
No problem with positve bound:
rasql -q 'UPDATE EU_DEM_32 SET EU_DEM_32[0:8820, 0:6769] ASSIGN decode(<[0:0] 1c>, "GDAL", "{\"filePaths\":[\"/home/rasdaman/tmp/test_eu_dem_parsec/EU_DEM_32_3035.tiff\"]}")' --user rasadmin --passwd rasadmin rasql: rasdaman query tool v1.0, rasdaman 10.0.0. Opening database RASBASE at 127.0.0.1:7001... ok. Executing update query... ok.
Change History (5)
comment:1 by , 4 years ago
Owner: | changed from | to
---|
comment:2 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
ok, I don't remember this shift(). It was not generated by petascope.
comment:3 by , 4 years ago
Yes I guess it's generated by petascope, that's why I reassigned to you: shouldn't petascope be fixed?
comment:4 by , 4 years ago
I mentioned, this query was not generated by petascope. I was trying to update manually a collection.
Note:
See TracTickets
for help on using tickets.
It's missing a shift with the negative bound, i.e. this should work:
It works with the positive bound without shift because
[0:8820, 0:6769]
starts at[0,0]
already.