[flink] Support parallelismConfigurable #5076
Open
+265
−103
Conversation
This file contains 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
yunfengzhou-hub
force-pushed
the
parallelism-configurable
branch
from
a07de06 to
0c9d99a
Compare
yunfengzhou-hub
force-pushed
the
parallelism-configurable
branch
from
0c9d99a to
60f5689
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
In Flink 1.17+, the parameter
parallelismConfigurableis introduced to support specifying operator's initial parallelism while dynamically changing parallelism in some situations (like in AQE). This PR adds this parameter to Paimon Flink operators where parallelism does not affect correctness, and can be changed by Flink infra according to detailed needs.Related PR: #4975
Tests
Flink batch execution mode enables AQE by default, so existing batch tests like BatchFileStoreITCase can verify the correctness of these changes.
API and Format
This change does not affect API or storage format.
Documentation
This change does not introduce a new feature that needs documentation.