-
Notifications
You must be signed in to change notification settings - Fork 688
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
TiCDC example include wrong values #19006
Comments
@3AceShowHand Would you please take a look at the following feedback and update the docs if necessary? Thanks. |
@choudharypankaj Can you explain in more detail, what's wrong with this example ? |
@3AceShowHand The value is wrong
shouldn't it be: "val":{"t":15,"v":"aa"}}}"] |
This example data was copied from the logs, those value is encoded. we have proposed PR to fix this. |
File: /release-8.1/ticdc/ticdc-open-protocol.md
INSERT INTO test.t1(id, val) VALUES (1, 'aa');
INSERT INTO test.t1(id, val) VALUES (2, 'aa')
From the following Log 5 and Log 6, you can see that Row Changed Events on the same table might be sent to different partitions based on the primary key, but changes to the same row are sent to the same partition so that the downstream can easily process the Event concurrently.
The corresponding output is wrong:
5. [partition=0] [key="{"ts":415508878783938562,"scm":"test","tbl":"t1","t":1}"] [value="{"u":{"id":{"t":3,"h":true,"v":1},"val":{"t":15,"v":"YWE="}}}"]
6. [partition=1] [key="{"ts":415508878783938562,"scm":"test","tbl":"t1","t":1}"] [value="{"u":{"id":{"t":3,"h":true,"v":2},"val":{"t":15,"v":"YmI="}}}"]
and so are the remaining output values
The text was updated successfully, but these errors were encountered: