-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
base: main
Are you sure you want to change the base?
Conversation
@pvary @stevenzwu Can you help me review it if you have time? Thanks a lot |
There was a problem hiding this 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!
@huyuanfeng2018: Could we have a unit test for this to avoid future regressions? |
Thanks @pvary and @mxm review~
done. @stevenzwu cc, Maybe you will be interested in this~ |
f2fed06
to
61f4c6f
Compare
out.collect(statisticsOrRecord.record()); | ||
} | ||
}) | ||
// Set the parallelism same as writerParallelism avoid broken chain |
There was a problem hiding this comment.
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.
There was a problem hiding this 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
fixed. PTAL |
Detailed: #11543
This fix will modify the data processing process in RANGE mode, set the filter link of
StatisticsOrRecord
and actively set it towriteParallelism
to avoid the shuffle mode changing to rebalance due to changes in parallelism in subsequent write operators.