Skip to content

branch-4.0: [fix](paimon) fix runtime partition prune on partition splits - #65308

Closed
suxiaogang223 wants to merge 1 commit into
apache:branch-4.0from
suxiaogang223:codex/fix-paimon-runtime-partition-prune-40
Closed

branch-4.0: [fix](paimon) fix runtime partition prune on partition splits#65308
suxiaogang223 wants to merge 1 commit into
apache:branch-4.0from
suxiaogang223:codex/fix-paimon-runtime-partition-prune-40

Conversation

@suxiaogang223

Copy link
Copy Markdown
Member

What problem does this PR solve?

Fixes wrong partition pruning for Paimon external table splits when runtime partition pruning evaluates static partition predicates such as partition IN (...).

The old BE path reused _runtime_filter_partition_prune_block across splits and inserted partition value columns by index. Repeated insert(index, ...) can corrupt the block column layout across splits, causing valid splits to be pruned incorrectly.

This also makes Paimon split partition metadata stable by passing ordered partition keys and values from FE to BE.

Related fix: #62821
Related Jira: DORIS-26857
Backport of branch-4.1 PR: #65307

Check List

  • Added regression coverage for Paimon partition pruning with multiple partition values.
  • Local build/regression not run; expected to be verified by CI.

@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?

@suxiaogang223
suxiaogang223force-pushed the codex/fix-paimon-runtime-partition-prune-40 branch from c11e30b to 4330653CompareJuly 7, 2026 07:38
@suxiaogang223suxiaogang223 changed the title [fix](paimon) fix runtime partition prune on partition splits[branch-4.0][fix](paimon) fix runtime partition prune on partition splitsJul 7, 2026
@suxiaogang223suxiaogang223 changed the title [branch-4.0][fix](paimon) fix runtime partition prune on partition splitsbranch-4.0: [fix](paimon) fix runtime partition prune on partition splitsJul 7, 2026
@suxiaogang223

Copy link
Copy Markdown
MemberAuthor

run buildall

@suxiaogang223
suxiaogang223force-pushed the codex/fix-paimon-runtime-partition-prune-40 branch from 4330653 to ed9903dCompareJuly 7, 2026 11:09
@suxiaogang223

Copy link
Copy Markdown
MemberAuthor

run buildall

@suxiaogang223
suxiaogang223force-pushed the codex/fix-paimon-runtime-partition-prune-40 branch from ed9903d to bdfc66bCompareJuly 8, 2026 01:59
@suxiaogang223

Copy link
Copy Markdown
MemberAuthor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 11.54% (6/52) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage71.49% (25572/35768)
Line Coverage54.36% (271085/498727)
Region Coverage51.90% (224620/432764)
Branch Coverage53.35% (96755/181344)

@suxiaogang223
suxiaogang223force-pushed the codex/fix-paimon-runtime-partition-prune-40 branch from bdfc66b to 5174a20CompareJuly 13, 2026 08:27
@suxiaogang223

Copy link
Copy Markdown
MemberAuthor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/56) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage53.51% (19564/36560)
Line Coverage36.59% (183075/500372)
Region Coverage33.15% (142308/429334)
Branch Coverage34.01% (61534/180925)

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 60.71% (34/56) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage71.46% (25560/35768)
Line Coverage54.40% (271322/498715)
Region Coverage52.05% (225252/432766)
Branch Coverage53.42% (96872/181347)

@suxiaogang223
suxiaogang223force-pushed the codex/fix-paimon-runtime-partition-prune-40 branch from 5174a20 to de3405eCompareJuly 13, 2026 11:46
@suxiaogang223

Copy link
Copy Markdown
MemberAuthor

run buildall

@suxiaogang223
suxiaogang223force-pushed the codex/fix-paimon-runtime-partition-prune-40 branch from de3405e to 8e86b57CompareJuly 13, 2026 11:48
@suxiaogang223

Copy link
Copy Markdown
MemberAuthor

run buildall

@suxiaogang223
suxiaogang223force-pushed the codex/fix-paimon-runtime-partition-prune-40 branch from 8e86b57 to dcee520CompareJuly 14, 2026 02:36
@suxiaogang223

Copy link
Copy Markdown
MemberAuthor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 60.38% (32/53) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage53.53% (19570/36560)
Line Coverage36.60% (183142/500372)
Region Coverage33.17% (142404/429338)
Branch Coverage34.02% (61549/180927)

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 73.58% (39/53) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage71.54% (25588/35768)
Line Coverage54.43% (271475/498715)
Region Coverage52.10% (225469/432770)
Branch Coverage53.47% (96972/181349)

@suxiaogang223
suxiaogang223force-pushed the codex/fix-paimon-runtime-partition-prune-40 branch from dcee520 to fa21976CompareJuly 14, 2026 06:41
@suxiaogang223

Copy link
Copy Markdown
MemberAuthor

run buildall

@suxiaogang223

Copy link
Copy Markdown
MemberAuthor

Superseded by #65583, which reimplements the fix from scratch on the latest release-branch baseline.

Sign up for freeto 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

@suxiaogang223@hello-stephen