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

Jump to bottom

ticdc: synchronize data in the new collations #8584

Merged
merged 2 commits into from
May 19, 2022
Merged

ticdc: synchronize data in the new collations #8584

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9b70c9c
ticdc: synchronize data in the new collations
shichun-0415 May 11, 2022
dc96aa7
Apply suggestions from code review
shichun-0415 May 19, 2022
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
12 changes: 6 additions & 6 deletions ticdc/manage-ticdc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -602,11 +602,7 @@ protocol = "canal-json"

## Output the historical value of a Row Changed Event <span class="version-mark">New in v4.0.5</span>

> **Warning:**
>
> Currently, outputting the historical value of a Row Changed Event is still an experimental feature. It is **NOT** recommended to use it in the production environment.

In the default configuration, the Row Changed Event of TiCDC Open Protocol output in a replication task only contains the changed value, not the value before the change. Therefore, the output value neither supports the [new collation framework](/character-set-and-collation.md#new-framework-for-collations) introduced in TiDB v4.0, nor can be used by the consumer ends of TiCDC Open Protocol as the historical value of a Row Changed Event.
In the default configuration, the Row Changed Event of TiCDC Open Protocol output in a replication task only contains the changed value, not the value before the change. Therefore, the output value cannot be used by the consumer ends of TiCDC Open Protocol as the historical value of a Row Changed Event.

Starting from v4.0.5, TiCDC supports outputting the historical value of a Row Changed Event. To enable this feature, specify the following configuration in the `changefeed` configuration file at the root level:

Expand All @@ -616,7 +612,11 @@ Starting from v4.0.5, TiCDC supports outputting the historical value of a Row Ch
enable-old-value = true
```

After this feature is enabled, you can see [TiCDC Open Protocol - Row Changed Event](/ticdc/ticdc-open-protocol.md#row-changed-event) for the detailed output format. The new TiDB v4.0 collation framework will also be supported when you use the MySQL sink.
This feature is enabled by default since v5.0. To learn the output format of the TiCDC Open Protocol after this feature is enabled, see [TiCDC Open Protocol - Row Changed Event](/ticdc/ticdc-open-protocol.md#row-changed-event).

## Replicate tables with the new framework for collations enabled

Starting from v4.0.15, v5.0.4, v5.1.1 and v5.2.0, TiCDC supports tables that have enabled [new framework for collations](/character-set-and-collation.md#new-framework-for-collations).

## Replicate tables without a valid index

Expand Down
2 changes: 1 addition & 1 deletion ticdc/troubleshoot-ticdc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -473,4 +473,4 @@ When the sink is TiDB or MySQL, the users of the downstream database need the fo
- `Alter`
- `Create View`

If you need to replicate `recover table` to the downstream TiDB, the `Super` permission is required.
If you need to replicate `recover table` to the downstream TiDB, you should have the `Super` permission.