How Asynchronous Run Query Works
When longrunquery is run with valid JSON input, it returns 202 status code along with a unique key, internally it accepts the request and starts processing requested query. Once the processing is completed, result is cached for configurable amount of time. User can access the result with same unique key until it is available in cache.
Processing status can be checked using longrunquery result end point by passing the key like /ebis/api/v1/dataservice (the /longrunquery/result/<Key> request should be appended with the key that got returned from the longrunquery), it returns following responses based on the status
- PROCESSING if the request query is still processing.
- Response in JSON format, if the request query is successfully executed and saved in cache.
- FAILED if the request query encounters any exception while processing.
Note: LongRunQuery response data for a specific key will be available in the system for only 60 minutes and after that response data will be deleted from system and key gets expired.
Last Published Tuesday, February 6, 2024