Thanks to visit codestin.com
Credit goes to Github.com

Skip to content

Conversation

@Seaven
Copy link
Contributor

@Seaven Seaven commented Jan 20, 2026

Why I'm doing:

What I'm doing:

Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
    • This pr needs auto generate documentation
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 4.1
    • 4.0
    • 3.5
    • 3.4

@Seaven Seaven requested a review from a team as a code owner January 20, 2026 03:44
@wanpengfei-git wanpengfei-git requested a review from a team January 20, 2026 03:44
@mergify mergify bot assigned Seaven Jan 20, 2026
@StarRocks-Reviewer
Copy link

@cursor review

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: eeec80aaf8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 4 potential issues.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

Signed-off-by: Seaven <[email protected]>
@alvin-celerdata
Copy link
Contributor

@codex review

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a7acd51954

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

return List.of();
}

Preconditions.checkState(partitionValuesList.size() == partitionCols.size());

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Fix list-partition range handling for multi-column values

In computePartitionRange the list-partition branch treats partitionValuesList as if its outer size equals the number of partition columns, but ListPartitionInfo.getMultiLiteralExprValues() returns a list of rows (each inner list contains values for all partition columns). That means Preconditions.checkState(partitionValuesList.size() == partitionCols.size()) will throw for typical multi-column list partitions (e.g., 2 columns with >2 list values), causing planning to fail as soon as partition pruning is enabled. Even if the sizes happen to match, the subsequent partitionValuesList.get(i) is a row, not the list of values for column i, so the TKeyRange values are misassigned. This should pivot rows into per-column lists (or validate inner list sizes) before building list_values.

Useful? React with 👍 / 👎.

Signed-off-by: Seaven <[email protected]>
Signed-off-by: Seaven <[email protected]>
Signed-off-by: Seaven <[email protected]>
@sonarqubecloud
Copy link

Signed-off-by: Seaven <[email protected]>
m
Signed-off-by: Seaven <[email protected]>
@github-actions
Copy link

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

@github-actions
Copy link

[BE Incremental Coverage Report]

fail : 0 / 91 (00.00%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 be/src/exec/olap_scan_node.cpp 0 91 00.00% [123, 124, 125, 126, 127, 131, 132, 433, 435, 436, 437, 438, 439, 441, 442, 444, 445, 446, 447, 448, 449, 450, 451, 452, 453, 454, 456, 457, 458, 459, 461, 462, 463, 464, 465, 466, 468, 469, 470, 471, 474, 475, 479, 481, 482, 483, 486, 487, 489, 490, 493, 494, 495, 496, 497, 498, 499, 503, 504, 505, 508, 509, 511, 512, 513, 515, 516, 517, 518, 520, 521, 522, 524, 525, 529, 530, 531, 532, 533, 536, 537, 539, 540, 543, 544, 545, 552, 554, 555, 560, 604]

@alvin-celerdata
Copy link
Contributor

@codex review

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c54873424d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants