ReferenceApplies to: Unified engine deployments
[gateway]
Settings
max_response_bytes
Limits the encoded size of one outgoing response.
- Default:
67108864
- Type: integer (bytes); positive
Example
67108864 gives one response a 64 MiB budget. A larger result can require smaller result pages rather than one larger response.
max_cached_relation_bytes
Limits the size of a serialized cached relation accepted by the client gateway.
- Default:
1048576
- Type: integer (bytes); positive
Example
1048576 allows a cached relation up to 1 MiB. It does not set the limit for all table data returned by a query.
max_plan_depth
Limits how deeply an incoming client plan may be nested.
- Default:
128
- Type: integer; positive
Example
128 bounds nesting to 128 levels. Deeply nested expressions can reach this limit even when the SQL text is short.
max_plan_nodes
Limits how many operations and expressions an incoming plan may contain.
- Default:
100000
- Type: integer; positive
Example
100000 bounds the plan’s node count. Raising the HTTP byte limit alone does not increase this count.
poll_interval
Sets how often the gateway checks query progress while waiting for a result.
- Default:
100 ms
- Type: duration
Example
{ secs = 0, nanos = 100000000 } checks about every 100 ms. A shorter interval makes more status requests.
result_page_size
Sets how many stored result batches the gateway requests in one read.
- Default:
16
- Type: integer; positive
Example
16 reads up to 16 batches per page. A batch can contain many rows; this does not mean 16 result rows.
execution_target
Chooses the engine expected to execute the task.
- Default:
"DuckDb"
- Type: choice:
DataFusion, DuckDb
Example
"DuckDb" selects Native Engine. DataFusion is another serialized target, but it needs a compatible executor; the current native worker starts Native Engine.
Last modified on November 4, 2026
