Skip to content

Conversation

@ferenc-csaky
Copy link
Contributor

No description provided.

@ferenc-csaky
Copy link
Contributor Author

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.

@lvyanquan
Copy link
Contributor

lvyanquan commented Feb 18, 2025

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.

Hi @ferenc-csaky, have you found out the cause, or is it just an accidental failure?

@ferenc-csaky ferenc-csaky force-pushed the FLINK-37152 branch 2 times, most recently from aec0014 to d2189d7 Compare February 18, 2025 12:02
@github-actions github-actions bot added the docs Improvements or additions to documentation label Feb 18, 2025
@ferenc-csaky
Copy link
Contributor Author

ferenc-csaky commented Feb 18, 2025

@lvyanquan seemed to be some intermittent issue, the CI I ran today succeeded at that step, but since in the meantime Flink 1.20.1 got released IMO it makes sense to update to that right away, so I updated 1.20.0 to 1.20.1 in all relevant places, except the CI.

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.

@github-actions github-actions bot removed the docs Improvements or additions to documentation label Feb 18, 2025
@ferenc-csaky
Copy link
Contributor Author

Well, exchanged the mongodb7 failure to a mysql one.. :) Will check on it tomorrow

@lvyanquan
Copy link
Contributor

Well, exchanged the mongodb7 failure to a mysql one.. :) Will check on it tomorrow

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.

Copy link
Contributor

@lvyanquan lvyanquan left a 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>
Copy link
Contributor

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?

Copy link
Contributor Author

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?

Copy link
Contributor

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.

@leonardBang
Copy link
Contributor

Well, exchanged the mongodb7 failure to a mysql one.. :) Will check on it tomorrow

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

@leonardBang leonardBang merged commit 0211a13 into apache:master Feb 20, 2025
30 of 31 checks passed
@leonardBang
Copy link
Contributor

Failed case tracked via https://issues.apache.org/jira/browse/FLINK-37362

@ferenc-csaky ferenc-csaky deleted the FLINK-37152 branch February 20, 2025 13:30
SML0127 pushed a commit to SML0127/flink-cdc-connectors that referenced this pull request Feb 21, 2025
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