Skip to content

branch-4.1: [fix](fe) Parse MaxCompute partition specs by name #64937#65227

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-64937-branch-4.1
Open

branch-4.1: [fix](fe) Parse MaxCompute partition specs by name #64937#65227
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-64937-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #64937

MaxCompute partition specs were parsed by fragment
position and silently accepted fragments whose column prefix did not
match the expected partition column. If a partition spec is not ordered
the same way as the table partition columns, Doris can bind values to
the wrong partition columns during internal partition pruning. This
change parses each fragment as name=value, rejects malformed, duplicate,
or unexpected partition columns, and returns values ordered by the table
partition column list.
@github-actions github-actions Bot requested a review from yiguolei as a code owner July 6, 2026 03:12
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 88.24% (15/17) 🎉
Increment coverage report
Complete coverage report

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants