Query inline orders

How-to guideApplies to: Unified engine deployments

Use only HTTP to count and summarize inline data. No files, catalog connection, or credentials are needed.

Query inline orders over HTTP

Expect Books 60, Games 45, and Garden 35. Send each step explicitly. Use the returned session ID in later requests.

Placeholder	Value
`{{operation_id}}`	A new UUID for this request; reuse it when recovering the same submission.

Replace the placeholders in your client. Keep returned IDs for later requests. Paths below use the native API prefix; adjust it for your deployment.

1. Open a session

POST /api/v1/sessions
Host: <ENGINE_HOST>

From the response, keep session_id from /session_id. Endpoint reference.

2. Submit SQL

POST /api/v1/sessions/{{session_id}}/operations
Host: <ENGINE_HOST>
Content-Type: application/json

{
  "operation_id": "{{operation_id}}",
  "sql": "WITH orders(id, category, region, amount) AS (VALUES (1, 'Books', 'North', 20), (2, 'Games', 'South', 30), (3, 'Games', 'North', 15), (4, 'Books', 'North', 40), (5, 'Garden', 'South', 25), (6, 'Garden', 'North', 10)) SELECT category, SUM(amount) AS sales FROM orders GROUP BY category ORDER BY category",
  "source": "external"
}

Endpoint reference.

3. Follow execution

GET /api/v1/sessions/{{session_id}}/operations/{{operation_id}}
Host: <ENGINE_HOST>

Repeat this read until /status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped. Endpoint reference.

4. Read result metadata

GET /api/v1/sessions/{{session_id}}/operations/{{operation_id}}/results/metadata
Host: <ENGINE_HOST>

Endpoint reference.

5. Fetch rows

GET /api/v1/sessions/{{session_id}}/operations/{{operation_id}}/results?limit=1
Host: <ENGINE_HOST>

Endpoint reference.

6. Close the session

DELETE /api/v1/sessions/{{session_id}}
Host: <ENGINE_HOST>

Endpoint reference.

Follow the steps

Open a session and keep its returned ID. Submit the SQL once. Use a unique operation ID and reuse it when recovering the same submission. Read operation status using the status request. Repeat until success or another final outcome. After success, read metadata and fetch one result page. Decode the Arrow response in your client to inspect the rows.

category	sales
Books	60
Games	45
Garden	35

Close the session when finished. Closing a session is a server operation; leaving the docs page is not cleanup.

Change the query

On a new submission, add WHERE region = 'North' before GROUP BY. Expect Books 60, Games 15, and Garden 10. Copy the SQL request and use a new operation ID in your own client. Keep the original request unchanged when recovering a lost response.

Transformation Engine

Learn Laminar

Workloads

SQL reference

HTTP API

Recipes

Operations

Query inline orders over HTTP

1. Open a session

2. Submit SQL

3. Follow execution

4. Read result metadata

5. Fetch rows

6. Close the session

Follow the steps

Change the query

​Query inline orders over HTTP

​1. Open a session

​2. Submit SQL

​3. Follow execution

​4. Read result metadata

​5. Fetch rows

​6. Close the session

​Follow the steps

​Change the query

Query inline orders over HTTP

1. Open a session

2. Submit SQL

3. Follow execution

4. Read result metadata

5. Fetch rows

6. Close the session

Follow the steps

Change the query