-
Notifications
You must be signed in to change notification settings - Fork 2k
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: Bump to Flink 1.15.3 #7059
Conversation
Auch!
Changed in #7059 |
a636fce
to
4c6b7b3
Compare
4c6b7b3
to
9db5f60
Compare
@@ -69,16 +73,20 @@ public SinkRuntimeProvider getSinkRuntimeProvider(Context context) { | |||
List<String> equalityColumns = | |||
tableSchema.getPrimaryKey().map(UniqueConstraint::getColumns).orElseGet(ImmutableList::of); | |||
|
|||
return (DataStreamSinkProvider) |
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.
I checked Flink code. Flink added a default implementation to the single abstract method in DataStreamSinkProvider
. Adding a default implementation usually is not considered as a breaking change, except for FunctionalInterface
in this case. But this class was never annotated with @FunctionalInterface
. Maybe we shouldn't have used the lambda function here at the first place.
We should fix the lambda usage regardless if we decided to update Flink patch version for compileOnly deps.
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.
Flink jira for this change: https://issues.apache.org/jira/browse/FLINK-28322
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.
With that, I am leaning toward not chasing the Flink patch release upgrades due to unnecessary overhead.
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.
I agree with not chasing Flink patch releases if they require code changes. I'd love to make sure they compile and work, but I wouldn't spend time tracking down errors between patch versions for third-party projects. If code changes are required, then we should stop update to a new patch version.
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.
That's a fair point. What you're saying is that the new version of Iceberg won't work with 1.15.0, 1.15.1, and 1.15.2 anymore, so we should not update. Makes sense to me.
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.
@Fokko I think it is still good to update code here (without bumping up Flink patch version). We should avoid using lambda function since DataStreamSinkProvider
is not annotated with @FunctionalInterface
.
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.
@stevenzwu Got it, I've removed the version bump for now.
@Fokko, I think we can skip this one since it requires code changes. |
thanks @Fokko |
No description provided.