-
Notifications
You must be signed in to change notification settings - Fork 287
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
Some transaction(s) could generate empty values in open protocol #2612
Closed
1 of 4 tasks
Tracked by
#2971
Labels
area/ticdc
Issues or PRs related to TiCDC.
component/open-protocol
Open TiCDC protocol component.
severity/major
type/bug
The issue is confirmed as a bug.
Comments
amyangfei
added
type/bug
The issue is confirmed as a bug.
component/open-protocol
Open TiCDC protocol component.
labels
Aug 24, 2021
amyangfei
changed the title
Some transaction could generate empty values in open protocol
Some transaction(s) could generate empty values in open protocol
Aug 24, 2021
This was referenced Aug 24, 2021
19 tasks
/assign I am working on the Canal JSON. |
|
canal:
|
maxwell:
|
arvo:
|
This was referenced Oct 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/ticdc
Issues or PRs related to TiCDC.
component/open-protocol
Open TiCDC protocol component.
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
What did you do? If possible, provide a recipe for reproducing the error.
What did you expect to see?
The mq sink should not output any row changes.
What did you see instead?
The following output using
kafka-console-consumer.sh
?{"ts":427235938124431362,"scm":"test","tbl":"t2","rid":2,"t":1} {}
The log of MySQL sink, note both
columns
andpre-columns
are emptyVersions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):All versions since v4.0.x
TiCDC version (execute
cdc version
):All versions since v4.0.x
Subtasks
The text was updated successfully, but these errors were encountered: