[Flink] Add option to avoid shuffle in bucket unaware append sink#7717
Merged
JingsongLi merged 1 commit intoMay 7, 2026
Merged
Conversation
nickdelnano
force-pushed
the
nickdelnano/bucket-unaware-append-no-shuffle
branch
7 times, most recently
from
ec17872 to
90c6196
Compare
nickdelnano
force-pushed
the
nickdelnano/bucket-unaware-append-no-shuffle
branch
from
90c6196 to
8f91105
Compare
Contributor
Author
|
@JingsongLi I saw you authored #4203 which relates to this PR, can you review it? |
Contributor
|
+1 |
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
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
Bucket unaware append table [1] is a great choice for streaming events into Paimon format for batch consumers. These types of streams can be very high throughput like clickstream data. Currently there is shuffle in the writer #4203 and in my production use cases (Kafka --> Paimon) this shuffles a lot of data.
rebalance was added to avoid chaining, instead we can use startNewChain. This can avoid the deadlock issue described in that PR without shuffle.
[1] https://cwiki.apache.org/confluence/display/PAIMON/PIP-6%3A+Unaware-Bucket+Table
Tests
FlinkCdcSyncTableSinkITCase.java has tests for schema evolution, however #4203 mentions this is hard to exercise in tests