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: Avoid RANGE mode broken chain when write parallelism changes #11702

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

huyuanfeng2018
Copy link
Contributor

Detailed: #11543

This fix will modify the data processing process in RANGE mode, set the filter link of StatisticsOrRecord and actively set it to writeParallelism to avoid the shuffle mode changing to rebalance due to changes in parallelism in subsequent write operators.

@github-actions github-actions bot added the flink label Dec 5, 2024
@huyuanfeng2018
Copy link
Contributor Author

@pvary @stevenzwu Can you help me review it if you have time? Thanks a lot

Copy link

@mxm mxm left a comment

Choose a reason for hiding this comment

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

Thanks for the fix!

@pvary
Copy link
Contributor

pvary commented Dec 13, 2024

@huyuanfeng2018: Could we have a unit test for this to avoid future regressions?

@huyuanfeng2018
Copy link
Contributor Author

huyuanfeng2018 commented Dec 17, 2024

Thanks @pvary and @mxm review~

@huyuanfeng2018: Could we have a unit test for this to avoid future regressions?

done.
TestFlinkIcebergSinkDistributionMode add unit test under different writeParallelism .

@stevenzwu cc, Maybe you will be interested in this~

out.collect(statisticsOrRecord.record());
}
})
// Set the parallelism same as writerParallelism avoid broken chain
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: maybe this?

Set the parallelism same as writerParallelism to promote operator chaining with the downstream writer operator.

Copy link
Contributor

@stevenzwu stevenzwu left a comment

Choose a reason for hiding this comment

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

just a nit comment

@huyuanfeng2018
Copy link
Contributor Author

just a nit comment

fixed. PTAL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants