Is your feature request related to a problem? Please describe.
- For a remote query we currently poll raw-data-api at an interval.
- Sometimes there is a large job queue for raw-data-api and the job may take time to complete.
- The polling interval increases up to a maximum duration of 10 minutes.
- This is fine for most use cases, as a response should likely return by then.
- However, some upstream services (e.g. FMTM) require a response in <1min if using during an API call, as the connection to the user will time out.
Describe the solution you'd like
- There should be an option for
execQuery to return the raw-data-api task ID only, so the upstream service can do the polling however they like (either websocket, or polling/heartbeat).
- A simple flag and early exit with the query URL would do the job.
Describe alternatives you've considered
- Increasing the timeout for the user request on a webserver, but this causes unnecessary load and is a bad idea.
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
execQueryto return the raw-data-api task ID only, so the upstream service can do the polling however they like (either websocket, or polling/heartbeat).Describe alternatives you've considered