-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[cdc-connector][sqlserver][tests] Fix UT errors by correcting right output #2864
Conversation
5d4ff4d
to
c190b49
Compare
c190b49
to
79bf604
Compare
@gong @leonardBang @GOODBOY008 , CC, before we fix #2853, fix the CI not to block other PR. |
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
@leonardBang , @GOODBOY008 , CC |
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.
+1
Thanks @loserwang1024 and @gong for the contribution, LGTM. Let's track this issue in #2853 |
As shown in #2853, SqlServer incremental source cannot support exactly-once now.
Between the time that a change is committed in the source table, and the time that the change appears in the corresponding change table, there is always a small latency interval.
Because the time is random, the test com.ververica.cdc.connectors.sqlserver.source.SqlServerSourceITCase#testEnableBackfillWithDMLPreHighWaterMark will sometime fail even sleep for 5 minute.
however, it's rather than tricky, may not be fixed recently. In oder to not influence other PR's CI , before #2853 is fixed, fix UT errors by correcting right output which includes duplicate data.