[core][flink] Support incremental clustering for append bucketed table #6835
Conversation
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
LsomeYeah
force-pushed
the
bucket-cluster
branch
from
1835c68 to
aedeea9
Compare
LsomeYeah
force-pushed
the
bucket-cluster
branch
from
aedeea9 to
692346a
Compare
JingsongLi
reviewed
Dec 24, 2025
Contributor
JingsongLi
left a comment
JingsongLi
left a comment
There was a problem hiding this comment.
My idea is that the clustering of this Bucketed table is like merging small files of Append+Bucket-1 table, directly generating tasks for different concurrent writer to reads and writes separately.
| runsInfo); | ||
| }); | ||
| } | ||
| partitionLevels.forEach( |
Contributor
There was a problem hiding this comment.
Too deep. Use for loop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Purpose
Linked issue: close #xxx
By default, Paimon's append bucketed tables maintain data ordering. However, this ordering requirement can be relaxed to enable additional optimizations.
This PR introduces the ability to disable ordering requirements for append bucketed tables, allowing incremental clustering within buckets. When ordering is not strictly required, data can be incrementally clustered within each bucket, significantly improving query performance for
bucket-key + clustering-keycombinations.Unlike append-unaware tables that require range partitioning, bucketed tables only need to shuffle by partition + bucket and perform local clustering within each bucket partition, making this approach much more efficient and resource-friendly.
Tests
API and Format
Documentation