Opened 3 months ago

Last modified 3 months ago

#1589 assigned defect

Rasql_Read query from a file when it is too long for bash

Reported by: bphamhuu Owned by:
Priority: major Milestone: Future
Component: rasql Version: development
Keywords: Cc: dmisev, vmerticariu, bbell, pbaumann
Complexity: Medium

Description (last modified by dmisev)

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 (6)

comment:1 Changed 3 months ago by bphamhuu

  • Description modified (diff)

comment:2 Changed 3 months ago by dmisev

  • Cc pbaumann added
  • Description modified (diff)
  • Owner set to jhalili
  • Status changed from new to assigned

comment:3 follow-up: Changed 3 months ago by 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.

comment:4 in reply to: ↑ 3 Changed 3 months ago by bphamhuu

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 Changed 3 months ago by vmerticariu

+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 Changed 3 months ago by dmisev

  • Milestone changed from 9.5 to Future
  • Owner jhalili deleted

Ok putting this to future, and expecting Bang to open another ticket regarding comment:4

Note: See TracTickets for help on using tickets.