Skip to content

Commit dbf6410

Browse files
pmbrullclaude
andauthored
feat(queryRunner): raise maxResultSize upper bound to 10000 (#27468)
* feat(queryRunner): raise maxResultSize upper bound to 100000 The previous 1000 cap forced admins to pick a conservative row limit for Query Runner executions even when their ingestion runner could comfortably return larger result sets. Raise the schema maximum to 100000 so operators have headroom to expose more rows to SQL Studio and downstream consumers. Enforcement and the default (100) are unchanged; the backend still injects the value from QueryRunnerConfig.querySettings.maxResultSize on every trigger, so this only widens the ceiling admins can opt into. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(queryRunner): lower maxResultSize ceiling from 100000 to 50000 Reviewer feedback: 50k is a better trade-off between giving admins headroom and keeping the batch workflow response from returning unwieldy payloads. Enforcement and defaults unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(queryRunner): further lower maxResultSize ceiling to 10000 Reviewer feedback: 10k is a more conservative ceiling that still gives admins meaningful headroom over the previous 1k cap while keeping payload sizes predictable through the batch workflow transport. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 25fda47 commit dbf6410

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

openmetadata-spec/src/main/resources/json/schema/entity/automations/queryRunnerRequest.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@
5858
"description": "RUNTIME FIELD - Automatically injected by backend from admin QueryRunnerConfig.querySettings.maxResultSize. This is NOT user-configurable in the request. The backend fetches this value from the service's QueryRunnerConfig and injects it here for enforcement by the Python workflow. If query has LIMIT exceeding this value, an error is raised. If query has no LIMIT, one is automatically injected.",
5959
"type": "integer",
6060
"minimum": 1,
61-
"maximum": 1000,
61+
"maximum": 10000,
6262
"default": null
6363
},
6464
"credentialSourceType": {

0 commit comments

Comments
 (0)