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.

Sign up for GitHub

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

v7.1.6: ticdc: add description for cdc behaviour change (#17530) (#17672) #19479

Merged
merged 2 commits into from
Nov 21, 2024
Merged

v7.1.6: ticdc: add description for cdc behaviour change (#17530) (#17672) #19479

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
015f181
This is an automated cherry-pick of #17672
ti-chi-bot Nov 21, 2024
93b6782
Apply suggestions from code review
qiancai Nov 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions ticdc/ticdc-split-update-behavior.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,11 @@ summary: Introduce the behavior changes about whether TiCDC splits `UPDATE` even

## Split `UPDATE` events for MySQL sinks

<<<<<<< HEAD
Starting from v6.5.10, v7.5.2, v8.1.1, and v8.2.0, when using the MySQL sink, any TiCDC node that receives a request for replicating a table will fetch the current timestamp `thresholdTS` from PD before starting the replication to the downstream. Based on the value of this timestamp, TiCDC decides whether to split `UPDATE` events:
=======
Starting from v6.5.10 and v7.1.6, when using the MySQL sink, any TiCDC node that receives a request for replicating a table will fetch the current timestamp `thresholdTS` from PD before starting the replication to the downstream. Based on the value of this timestamp, TiCDC decides whether to split `UPDATE` events:
>>>>>>> c52f64d595 (v7.1.6: ticdc: add description for cdc behaviour change (#17530) (#17672))
qiancai marked this conversation as resolved.
Show resolved Hide resolved

- For transactions containing one or multiple `UPDATE` changes, if the transaction `commitTS` is less than `thresholdTS`, TiCDC splits the `UPDATE` event into a `DELETE` event and an `INSERT` event before writing them to the Sorter module.
- For `UPDATE` events with the transaction `commitTS` greater than or equal to `thresholdTS`, TiCDC does not split them. For more information, see GitHub issue [#10918](https://github.com/pingcap/tiflow/issues/10918).
Expand Down Expand Up @@ -142,6 +146,7 @@ Starting from v6.5.10, v7.1.6, v7.5.3, and v8.1.1, when using a non-MySQL sink,
| v7.1.1 | Canal/Open | ✗ | ✓ | |
| v7.1.1 | CSV/Avro | ✗ | ✗ | Split but does not sort. See [#9086](https://github.com/pingcap/tiflow/issues/9658) |
| v7.1.2 ~ v7.1.5 | ALL | ✓ | ✗ | |
<<<<<<< HEAD
| \>= v7.1.6 (not released yet) | ALL | ✓ (Default value: `output-raw-change-event = false`) | ✓ (Optional: `output-raw-change-event = true`) | |
qiancai marked this conversation as resolved.
Show resolved Hide resolved

#### Release 7.5 compatibility
Expand All @@ -157,3 +162,6 @@ Starting from v6.5.10, v7.1.6, v7.5.3, and v8.1.1, when using a non-MySQL sink,
| -- | -- | -- | -- | -- |
| v8.1.0 | ALL | ✓ | ✗ |
| \>= v8.1.1 | ALL | ✓ (Default value:`output-raw-change-event = false`) | ✓ (Optional: `output-raw-change-event = true`) | |
=======
| \>= v7.1.6 | ALL | ✓ (Default value: `output-raw-change-event = false`) | ✓ (Optional: `output-raw-change-event = true`) | |
>>>>>>> c52f64d595 (v7.1.6: ticdc: add description for cdc behaviour change (#17530) (#17672))
qiancai marked this conversation as resolved.
Show resolved Hide resolved
Loading