-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[FLINK-37152][build] Update Flink version to 1.20 #3868
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
Conversation
|
The mongodb7 CI failure is interesting, cause it ran without problem locally (on macOS). The test times out, I'm just downloading the logs, will check it out. |
flink-cdc-connect/flink-cdc-pipeline-connectors/flink-cdc-pipeline-connector-starrocks/pom.xml
Show resolved
Hide resolved
Hi @ferenc-csaky, have you found out the cause, or is it just an accidental failure? |
f4f9f89 to
c952740
Compare
aec0014 to
d2189d7
Compare
d2189d7 to
d9818fd
Compare
|
@lvyanquan seemed to be some intermittent issue, the CI I ran today succeeded at that step, After I saw that updating the patch version affects the doc build, I quickly reconsidered my previous plan and since at one pont 1.19.0 has to be updated anyway it probably easier to keep this change as minimal as possible. |
d9818fd to
2254071
Compare
|
Well, exchanged the |
I think that the failure of mysql is unrelated to the change here, because this error also occurs on the master branch, I will also try to identify the cause of this problem. |
lvyanquan
left a comment
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.
LGTM.
| <!-- dependencies versions --> | ||
| <flink.version>1.19.1</flink.version> | ||
| <flink.major.version>1.19</flink.major.version> | ||
| <flink.version>1.20.0</flink.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.
@ferenc-csaky Could you bump this version to 1.20.1 as we just released it?
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 was my original idea as well, but that generated more and more changes (docs, CI, etc), and 1.19.1 has to be bumped to 1.19.2 as well anyways. I'm happy to update both patch versions in a follow-up PR in 1 chunk. WDYT?
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.
As they're hotfix versions, follow-up PR makes sense to me, thanks for your quick response.
It's a known issue, maybe related to polardbx docker image, I've connected with the polardbx feature contributor, and he will look into this failure, FYI |
|
Failed case tracked via https://issues.apache.org/jira/browse/FLINK-37362 |
No description provided.