-
Notifications
You must be signed in to change notification settings - Fork 696
ticdc: add new doc for TiCDC data replication capabilities #20967
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
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
5c19785
update
hongyunyan 8e12b2e
Update ticdc/ticdc-data-sync-capabilities.md
hongyunyan d55061c
Update ticdc/ticdc-data-sync-capabilities.md
hongyunyan 8b9a3ef
Update ticdc/ticdc-data-sync-capabilities.md
hongyunyan 6b5aa8a
Update ticdc/ticdc-data-sync-capabilities.md
hongyunyan 19e9071
Update ticdc/ticdc-data-sync-capabilities.md
hongyunyan b9b7e1e
Update ticdc/ticdc-data-sync-capabilities.md
hongyunyan c7519f2
Update ticdc/ticdc-data-sync-capabilities.md
hongyunyan 81c003a
update
hongyunyan 4678d32
update
hongyunyan e0a0ee6
update
hongyunyan 1db77d7
Apply suggestions from code review
lilin90 09d55c7
Update wording
lilin90 91c5f17
Improve descriptions to make them clear
lilin90 686b419
Apply suggestions from code review
lilin90 41a34c8
Update a link
lilin90 03f3b29
Fix a link to pass check
lilin90 eb377e7
update
hongyunyan dae0011
Update ticdc/ticdc-data-replication-capabilities.md
flowbehappy c902e71
Improve wording
lilin90 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
--- | ||
title: TiCDC Data Replication Capabilities | ||
summary: Learn the data replication capabilities of TiCDC. | ||
--- | ||
|
||
# TiCDC Data Replication Capabilities | ||
|
||
[TiCDC](/ticdc/ticdc-overview.md) (TiDB Change Data Capture) is a core component in the TiDB ecosystem for real-time data replication. This document provides a detailed explanation of TiCDC data replication capabilities. | ||
|
||
## How TiCDC works | ||
|
||
- TiCDC listens to TiKV change logs (Raft logs) and converts row-level data changes (`INSERT`, `UPDATE`, and `DELETE` operations) into downstream-compatible SQL statements. TiCDC does not rely on the original SQL statements executed on the upstream database. For details, see [how TiCDC processes data changes](/ticdc/ticdc-overview.md#implementation-of-processing-data-changes). | ||
|
||
- TiCDC generates logical operations (such as `INSERT`, `UPDATE`, and `DELETE`) equivalent to SQL semantics, rather than restoring the original SQL statements executed on the upstream database one by one. For details, see [how TiCDC processes data changes](/ticdc/ticdc-overview.md#implementation-of-processing-data-changes). | ||
|
||
- TiCDC ensures eventual consistency of transactions. With [redo log](/ticdc/ticdc-sink-to-mysql.md#eventually-consistent-replication-in-disaster-scenarios) enabled, TiCDC can guarantee eventual consistency in disaster recovery scenarios. With [Syncpoint](/ticdc/ticdc-upstream-downstream-check.md#enable-syncpoint) enabled, TiCDC supports consistent snapshot reads and data consistency validation. | ||
|
||
## Supported downstream systems | ||
|
||
TiCDC supports replicating data to various downstream systems, including the following: | ||
|
||
- [TiDB database or other MySQL-compatible databases](/ticdc/ticdc-sink-to-mysql.md) | ||
- [Apache Kafka](/ticdc/ticdc-sink-to-kafka.md) | ||
- [Message Queue (MQ)-type sinks](/ticdc/ticdc-changefeed-config.md#sink), such as [Pulsar](/ticdc/ticdc-sink-to-pulsar.md) | ||
- [Storage services (Amazon S3, GCS, Azure Blob Storage, and NFS)](/ticdc/ticdc-sink-to-cloud-storage.md) | ||
- [Snowflake, ksqlDB, SQL Server via Confluent Cloud integration](/ticdc/integrate-confluent-using-ticdc.md) | ||
- [Apache Flink for consuming Kafka-replicated data](/replicate-data-to-kafka.md) | ||
|
||
## Scope of data replication | ||
|
||
TiCDC supports the following types of upstream data changes: | ||
|
||
+ **Supported:** | ||
|
||
- DDL and DML statements(excluding system tables). | ||
- Index operations (`ADD INDEX`, `CREATE INDEX`): to reduce the impact on changefeed replication latency, if the downstream is TiDB, TiCDC [asynchronously executes the `ADD INDEX` and `CREATE INDEX` DDL operations](/ticdc/ticdc-ddl.md#asynchronous-execution-of-add-index-and-create-index-ddls). | ||
- Foreign key constraint DDL statements (`ADD FOREIGN KEY`): TiCDC does **not** replicate upstream system variable settings. You need to manually configure [`foreign_key_checks`](/system-variables.md#foreign_key_checks) in the downstream to determine whether the downstream foreign key constraint check is enabled. TiCDC does **not** validate whether the data complies with foreign key constraints. | ||
|
||
+ **Not supported**: | ||
|
||
- DDL and DML statements executed in upstream system tables (including `mysql.*` and `information_schema.*`). | ||
- DDL and DML statements executed in upstream temporary tables. | ||
- DQL (Data Query Language) and DCL (Data Control Language) statements. | ||
|
||
## Limitations | ||
|
||
- TiCDC does not support certain scenarios. For details, see [unsupported scenarios](/ticdc/ticdc-overview.md#unsupported-scenarios). | ||
- TiCDC only verifies the integrity of upstream data changes. It does not validate whether the changes conform to upstream or downstream constraints. If the data violates downstream constraints, TiCDC will return an error when writing to the downstream. For example, TiCDC does **not** perform any foreign key validation. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.