-
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-35128][cdc-connector][cdc-base] Re-calculate the starting changelog offset after the new table added #3230
Conversation
@PatrickRen , @morazow , CC |
...c-base/src/main/java/org/apache/flink/cdc/connectors/base/source/meta/split/StreamSplit.java
Outdated
Show resolved
Hide resolved
59b1828
to
076eab9
Compare
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 @loserwang1024 for the PR!
I have minor question about choosing highWatermarks.
...c-base/src/main/java/org/apache/flink/cdc/connectors/base/source/meta/split/StreamSplit.java
Show resolved
Hide resolved
…gelog offset after the new table added
…gelog offset after the new table added
076eab9
to
ca98c09
Compare
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.
@loserwang1024 Thanks for the patch! LGTM
…gelog offset after the new table added (apache#3230) (cherry picked from commit bdca0e3)
…gelog offset after the new table added (apache#3230)
…gelog offset after the new table added (apache#3230)
In mysql cdc, re-calculate the starting binlog offset after the new table added in MySqlBinlogSplit#appendFinishedSplitInfos, while there lack of same action in StreamSplit#appendFinishedSplitInfos. This will cause data loss if any newly added table snapshot split's high_watermark is smaller.
Some unstable test problem occurs because of it.