Opened 7 years ago
Closed 7 years ago
#1589 closed defect (fixed)
Rasql_Read query from a file when it is too long for bash
Reported by: | Bang Pham Huu | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | Future |
Component: | rasql | Version: | development |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu, bbell, Peter Baumann | |
Complexity: | Medium |
Description (last modified by )
For big GRIB file (see here for a small query: https://pastebin.com/ui4WPUpC), the rasql query to update collection exceeds the maximum characters for bash (terminal) with the error "Argument list too long", example: http://earthserver.eu/trac2/ticket/225
So rasql should read the big query from a file like this
rasql --queryfile 'FILE_PATH'
This should be implemented in source:applications/rasql/rasql.cc
Change History (7)
comment:1 by , 7 years ago
Description: | modified (diff) |
---|
comment:2 by , 7 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Owner: | set to |
Status: | new → assigned |
follow-up: 4 comment:3 by , 7 years ago
comment:4 by , 7 years ago
Replying to dmisev:
Question: why don't we execute the query via rasj, and instead use rasql in WCS-T?
Now that the file for ingestion is specified in the decode parameter "filePath", we could simply use rasj.
yes, should be posible to use rasj instead of running with rasql by bash as other Rasql queries.
comment:5 by , 7 years ago
+1 for switching to rasj, the only reason we chose rasql was to avoid loading the binary data in java, as this was the only option of sending it to rasdaman via rasj at the time.
comment:6 by , 7 years ago
Milestone: | 9.5 → Future |
---|---|
Owner: | removed |
Ok putting this to future, and expecting Bang to open another ticket regarding comment:4
comment:7 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Ok so this ticket has actually been solved as far as I know and we can close it.
Question: why don't we execute the query via rasj, and instead use rasql in WCS-T?
Now that the file for ingestion is specified in the decode parameter "filePath", we could simply use rasj.