Start a query execution

POST 
/queries

Submits a SQL statement for asynchronous execution against Athena or Redshift and returns the identifier of the new execution. A 200 means the query was accepted, not that it has finished: poll GET /queries/{queryid} for the state and GET /queries/{queryid}/results for the result set.

Be aware that two input errors on this operation are returned as HTTP 500 rather than 400, because the handler raises them as backend exceptions: an unsupported WorkGroup (DWH-1033) and selecting QueryTargetLocation "redshift" in an environment whose datalake is not Redshift (GE-1036).

Request

Responses

200

Query accepted for execution. The body carries the identifier to poll for status and results.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

400

Input validation or authorization failure. Body is {"Message": " - "}. Codes: IPV-1008 (QueryString missing), IPV-1045 (QueryString or Encoding empty/invalid), IPV-1041 (unknown QueryTargetLocation), IPV-1069 (statement not supported for the selected engine), IPV-1071 (MERGE INTO run under the wrong workgroup), GE-1034 (QueryString is not valid base64), AUTH-1001 / AUTH-1030 / GE-1060 (authorization).

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

500

Backend failure, and also two input conditions the handler raises as backend exceptions: DWH-1033 (unsupported WorkGroup) and GE-1036 (QueryTargetLocation "redshift" on a non-Redshift datalake). Body is {"Message": " - "}.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers