Commit dbf6410
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
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
58 | 58 | | |
59 | 59 | | |
60 | 60 | | |
61 | | - | |
| 61 | + | |
62 | 62 | | |
63 | 63 | | |
64 | 64 | | |
| |||
0 commit comments