Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-35713][cdc-compose] Add sink PARALLELISM for flink-cdc. #3438

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

proletarians
Copy link
Contributor

No description provided.

@yuxiqian
Copy link
Contributor

Thanks for @proletarians' contribution! Kindly remind that mvn spotless:apply should be run before committing to fix any code style violations.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the future, defining multiple sink in one single pipeline job might be supported, and one might want to define parallelisms for each sink individually. Will it be better if we put sink.parallelism as an option in sink: block instead of a global pipeline option?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it! I will follow up on this.

@@ -93,6 +93,7 @@ private FlinkPipelineComposer(StreamExecutionEnvironment env, boolean isBlocking
@Override
public PipelineExecution compose(PipelineDef pipelineDef) {
int parallelism = pipelineDef.getConfig().get(PipelineOptions.PIPELINE_PARALLELISM);
int sinkParallelism = pipelineDef.getConfig().get(PipelineOptions.SINK_PARALLELISM);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if users do not set the SINK_PARALLELISM setting?

ConfigOptions.key("sink.parallelism")
.intType()
.noDefaultValue()
.withDescription("Parallelism of the sink in the pipeline");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add some tests for the setting.

@yuxiqian
Copy link
Contributor

Hi @proletarians, you may want to create individual branches for each PR to avoid mixing different changes together.

Copy link

This pull request has been automatically marked as stale because it has not had recent activity for 60 days. It will be closed in 30 days if no further activity occurs.

@github-actions github-actions bot added the Stale label Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants