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

[mysql] polish binlog offset compare semantic #543

Merged
merged 2 commits into from Nov 4, 2021
Merged

[mysql] polish binlog offset compare semantic #543

merged 2 commits into from Nov 4, 2021

Conversation

zhjwpku
Copy link
Contributor

@zhjwpku zhjwpku commented Nov 1, 2021

the isAtOrBefore & isBefore was actually meaning
isAtOrAfter & isAfter, so let's do this right ;)

Signed-off-by: Zhao Junwang zhjwpku@gmail.com

@zhjwpku zhjwpku changed the title [MySqlCDC] polish binlog offset compare semantic [mysql] polish binlog offset compare semantic Nov 1, 2021
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 @zhjwpku for the contribution, I left one comment

元组 added 2 commits November 2, 2021 18:35
the `isAtOrBefore & isBefore` was actually meaning
`isAtOrAfter & isAfter`, so let's do this right ;)

Signed-off-by: Zhao Junwang <zhjwpku@gmail.com>
1. HighWatermark itself should not be emitted
2. If the highWatermark equals maxHighWatermark, tableIdBinlogPositionMap doesn't need to change
3. change `compareTo < 0` to the more understandable isBefore

Signed-off-by: Zhao Junwang <zhjwpku@gmail.com>
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.

None yet

2 participants