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.

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: add 4 docs for data replication scenarios #10276

Merged
merged 34 commits into from
Jul 7, 2022

Conversation

shichun-0415
Copy link
Contributor

@shichun-0415 shichun-0415 commented Jun 27, 2022

First-time contributors' checklist

What is changed, added or deleted? (Required)

Suggestion from Allen Gao:
建议增加一个数据集成 一级目录来记录和TiCDC 相关的信息。内容上可以参考 migrate 部分。

  • 数据集成 overview: 数据集成的基本信息和 TiCDC 工具介绍。
  • 数据集成 scenarios:
    • 与 Confluent Cloud 进行数据集成
    • 与 Apache Kafka 和 Apache Flink 进行数据集成

在数据迁移目录下增加《从 TiDB 同步到 MySQL 兼容数据库》

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

  • master (the latest development version)
  • v6.2 (TiDB 6.2 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Jun 27, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • lilin90

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot requested a review from TomShawn June 27, 2022 15:56
@ti-chi-bot ti-chi-bot added missing-translation-status This PR does not have translation status info. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 27, 2022
@shichun-0415 shichun-0415 added type/refactor The issue belongs to a refactor work. translation/doing This PR’s assignee is translating this PR. area/ticdc Indicates that the Issue or PR belongs to the area of TiCDC. needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. and removed missing-translation-status This PR does not have translation status info. labels Jun 27, 2022
@shichun-0415 shichun-0415 self-assigned this Jun 27, 2022
@shichun-0415 shichun-0415 requested review from zier-one and removed request for TomShawn June 27, 2022 16:07
TOC.md Outdated Show resolved Hide resolved
TOC.md Outdated Show resolved Hide resolved
TOC.md Outdated Show resolved Hide resolved
migrate-from-tidb-to-mysql.md Outdated Show resolved Hide resolved
migrate-from-tidb-to-mysql.md Outdated Show resolved Hide resolved
migrate-from-tidb-to-mysql.md Outdated Show resolved Hide resolved
replicate-from-tidb-to-confluent.md Outdated Show resolved Hide resolved
replicate-from-tidb-to-confluent.md Outdated Show resolved Hide resolved
replicate-from-tidb-to-kafka-flink.md Outdated Show resolved Hide resolved
replication-overview.md Outdated Show resolved Hide resolved
replication-overview.md Outdated Show resolved Hide resolved
replicate-data-to-kafka.md Outdated Show resolved Hide resolved
ticdc/integrate-confluent-using-ticdc.md Outdated Show resolved Hide resolved
Copy link
Member

@lilin90 lilin90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Jul 7, 2022
@shichun-0415
Copy link
Contributor Author

/remove status LGT1
/status LGT2

@ti-chi-bot ti-chi-bot added the status/LGT2 Indicates that a PR has LGTM 2. label Jul 7, 2022
@shichun-0415
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: b04a904

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jul 7, 2022
@ti-chi-bot ti-chi-bot merged commit 9d231a0 into pingcap:master Jul 7, 2022
ti-chi-bot pushed a commit to ti-chi-bot/docs-cn that referenced this pull request Jul 7, 2022
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #10409.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ticdc Indicates that the Issue or PR belongs to the area of TiCDC. needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. status/LGT2 Indicates that a PR has LGTM 2. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. type/refactor The issue belongs to a refactor work.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants