[Enhancement] Improve error messages for large column capacity limit checks#76303
Merged
kevincai merged 1 commit intoJul 14, 2026
Merged
Conversation
Signed-off-by: cccaarr <jiangxiaoyu@starrocks.com>
|
@codex review |
Contributor
[Java-Extensions Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
Contributor
[FE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
kevincai
approved these changes
Jul 13, 2026
kevincai
enabled auto-merge (squash)
July 13, 2026 16:25
Contributor
[BE Incremental Coverage Report]✅ pass : 4 / 4 (100.00%) file detail
|
srlch
approved these changes
Jul 14, 2026
Contributor
|
@Mergifyio backport branch-4.0 |
Contributor
|
@Mergifyio backport branch-4.1 |
Contributor
|
@Mergifyio backport branch-3.5 |
Contributor
✅ Backports have been createdDetails
|
Contributor
✅ Backports have been createdDetails
|
Contributor
✅ Backports have been createdDetails
|
This was referenced Jul 14, 2026
Merged
[Enhancement] Improve error messages for large column capacity limit checks (backport #76303)
#76335
Merged
23 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why I'm doing:
When the large-column capacity checker trips, the error returned to the client
embedded internal diagnostics — the driver's raw pointer (
addr=this) and thefull operator chain from
to_readable_string(). That is internal debugginginformation that should not reach end users, and it gives them nothing
actionable. Separately, the shared status string for
CAPACITY_LIMIT_EXCEEDhad a typo ("Capaticy").
What I'm doing:
Capaticy->Capacityin the shared status string(
code_as_string), which is the common prefix for allCapacityLimitExceedresults.(operator index/name, query id, driver address, full operator chain) in
be.WARNINGfor operators/developers, and return a concise, actionablemessage to the client instead:
Large column detected, please reduce rows per batch or the size of string/array valuesNo functional change — the guard still trips on the same condition; only the
user-visible message text and the destination of the internal diagnostics change.
Fixes #76302
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: