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

TiCDC: Update ticdc-overview.md #2694

Merged
merged 6 commits into from
Jun 8, 2020
Merged

TiCDC: Update ticdc-overview.md #2694

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
3e61204
Update ticdc-overview.md
toutdesuite Jun 5, 2020
f28a446
update wording
toutdesuite Jun 5, 2020
1e50dc9
Update ticdc/ticdc-overview.md
ran-huang Jun 5, 2020
1d20611
Merge branch 'master' into ticdc-overview
ran-huang Jun 5, 2020
f4e5c71
Update ticdc/ticdc-overview.md
toutdesuite Jun 5, 2020
b914597
Merge branch 'master' into ticdc-overview
sre-bot Jun 8, 2020
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
Prev Previous commit
Next Next commit
update wording
  • Loading branch information
@toutdesuite
toutdesuite committed Jun 5, 2020
commit f28a446c35d1eadf0d46ea2ae2674b5f407a915c
6 changes: 3 additions & 3 deletions ticdc/ticdc-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,11 +54,11 @@ To replicate data to TiDB or MySQL, you must ensure that the following requireme

### Unsupported scenarios

Currently, the unsupported scenarios are as follows:
Currently, The following scenarios are not supported:

- The replication of partition tables.
toutdesuite marked this conversation as resolved.
Show resolved Hide resolved
- TiKV clusters that use RawKV alone.
- The [new framework for collations](/character-set-and-collation.md#new-framework-for-collations) in TiDB v4.0. Before you enable this feature, make sure that the downstream cluster is the TiDB cluster with the same collation as the upstream; otherwise, the inconsistent collation leads to an issue that the data cannot be located.
- The TiKV cluster that uses RawKV alone.
- The [new framework for collations](/character-set-and-collation.md#new-framework-for-collations) in TiDB v4.0. Before you enable this feature, make sure that the downstream cluster is the TiDB cluster with the same collation as those in the upstream; otherwise, inconsistent collations lead to the issue that the data cannot be located.
- [The DDL operation `CREATE SEQUENCE`](/sql-statements/sql-statement-create-sequence.md) and the [SEQUENCE function](/sql-statements/sql-statement-create-sequence.md#sequence-function) in TiDB v4.0. When the upstream TiDB uses SEQUENCE, TiCDC ignores SEQUENCE DDL operations/functions performed upstream. However, DML operations using SEQUENCE functions can be correctly replicated.
ran-huang marked this conversation as resolved.
Show resolved Hide resolved
- The [TiKV Hibernate Region](https://github.com/tikv/tikv/blob/master/docs/reference/configuration/raftstore-config.md#hibernate-region). TiCDC prevents the Region from entering the hibernated state.
- The scheduling of existing replication tables to new TiCDC nodes, after the capacity of the TiCDC cluster is scaled out.
Expand Down