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

Cherry pick bugfix commits for Release 2.4.2 #2591

Merged
merged 31 commits into from
Oct 31, 2023

Conversation

GOODBOY008
Copy link
Member

Cherry pick bugfix commits for Release 2.4.2.
69dcbabed4ace81837e139ca50a8d718
58653833d8870608be3bdfc4084912d6
497defa6704a6ce8d20d355d379f236b

@GOODBOY008
Copy link
Member Author

企业微信截图_16986373911511 @Jiabao-Sun Becasuse the first commit depends on the under three commits, so I add the under three commit to 2.4.2.

Copy link
Contributor

@leonardBang leonardBang left a comment

Choose a reason for hiding this comment

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

Thanks @GOODBOY008 for the great work, I left some comments about API change commits, I think we should only introduce the bugfix commits for bugfix version.

* produces full changelog mode structure {@link RowData}.
*/
@PublicEvolving
public class MongoDBConnectorFullChangelogDeserializationSchema
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a feature with public API change, I'm not sure we can pick this or not, I tend to skip this one

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks @leonardBang, it makes sense to me.
The supports of MongoDB 6.0 will indeed affect the API, but it will maintain compatibility with the old version under the default configuration. I tend to skip this one as well.

Copy link
Contributor

Choose a reason for hiding this comment

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

* <p>See more
* https://cwiki.apache.org/confluence/display/FLINK/FLIP-147%3A+Support+Checkpoints+After+Tasks+Finished.
*/
public PostgresSourceBuilder<T> closeIdleReaders(boolean closeIdleReaders) {
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be a API change feature?

Copy link
Contributor

Choose a reason for hiding this comment

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

There is no API change, here is something omitted here at 2.3

/** VTCtld server config. */
public Builder<T> vtctldConfig(VtctldConfig vtctldConfig) {
this.vtctldConfig = vtctldConfig;
/**
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like we pick some features

Copy link
Member Author

@GOODBOY008 GOODBOY008 Oct 30, 2023

Choose a reason for hiding this comment

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

These changes belong to [vitess] Migrate connector properties to debezium 1.9.7 (#2260). It's ok to merge this commit.

Copy link
Member Author

Choose a reason for hiding this comment

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

I understand your concern and drop this commit.

@GOODBOY008
Copy link
Member Author

企业微信截图_16986373911511 @Jiabao-Sun Becasuse the first commit depends on the under three commits, so I add the under three commit to 2.4.2.

@leonardBang About mongodb hotfix, I added under three commits because upper bugfix depend on them. I confirmed with @Jiabao-Sun , he think it's ok to add this three commits.

@leonardBang
Copy link
Contributor

leonardBang commented Oct 30, 2023

@GOODBOY008 @Jiabao-Sun Keep API compatible is pretty important, we need ensure that all users who use Flink CDC 2.4.0& 2.4.1 can bump to Flink CDC 2.4.2 without any SQL/code change, I'm not sure this PR would break this constraint or not, looks like this PR would break this?

senlizishi and others added 23 commits October 30, 2023 15:39
…xx = database, schema or table) (apache#2212)

(cherry picked from commit ba5fcbc)
…m for Oracle CDC Connector

This closes apache#2325.

Co-authored-by: skylines <[email protected]>
(cherry picked from commit 65bdbfd)
…ailedSource (apache#2384)

* [hotfix][mysql] fix failed test LegacyMySqlSourceTest#testSnapshotOnFailedSource

* [hotfix][mysql] fix failed test LegacyMySqlSourceTest#testSnapshotOnFailedSource

(cherry picked from commit b8f468e)
This closes #apache#2362.
Co-authored-by: TJX2014 <[email protected]>

(cherry picked from commit 094fff4)
…pleTest#testConsumingAllEvents (apache#2364)

(cherry picked from commit a3ddc48)
apache#2388)

Co-authored-by: DESKTOP-TQDONF3\狗狗jian <[email protected]>
(cherry picked from commit f7df47e)
* [sqlserver] Fix backfill stream task hang

* [sqlserver] Fix backfill stream task hang

(cherry picked from commit 6fa02ef)
* [oracle] Correct the naming error

* Fix comments

* fix name error

(cherry picked from commit 8feb51b)
… calculation

This closes apache#2421.

Co-authored-by: Leonard Xu <[email protected]>
(cherry picked from commit dddab4d)
@GOODBOY008
Copy link
Member Author

17a16e79b367a56ddd9e3cc6ceddcd72 @Jiabao-Sun I just pick the two commits, PTAL.

@lvyanquan
Copy link
Contributor

LGTM, +1

@leonardBang
Copy link
Contributor

The CI failed even I triggered retry, @GOODBOY008 @lvyanquan could you take a look ?

@GOODBOY008
Copy link
Member Author

The CI failed even I triggered retry, @GOODBOY008 @lvyanquan could you take a look ?

Yes,I am trying to find out reason.

Copy link
Contributor

@leonardBang leonardBang left a comment

Choose a reason for hiding this comment

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

Thank all for this PR, especially thanks @GOODBOY008 for preparing the PR and
troubleshooting the CI failure, LGTM

@leonardBang leonardBang merged commit 80cd840 into apache:release-2.4 Oct 31, 2023
15 checks passed
@GOODBOY008 GOODBOY008 deleted the release-2.4 branch January 11, 2024 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.