Skip to content

ticdc, dm: fix wrong values, a parameter name, and identifiers in TiCDC and DM docs - #24488

Open
yahonda wants to merge 3 commits into
pingcap:masterfrom
yahonda:ticdc-dm-fix-wrong-values-and-flags
Open

yahonda wants to merge 3 commits into
pingcap:masterfrom
yahonda:ticdc-dm-fix-wrong-values-and-flags

Conversation

@yahonda

@yahonda yahonda commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

What is changed, added, or deleted? (Required)

Fix wrong values, a parameter name, and identifiers in the TiCDC and DM docs. These errors were found while reviewing the English docs for issues that affect the Japanese translation. Each fix is shown below; the same wrong text was also searched for in the rest of the docs.

File Before After
ticdc/ticdc-sink-to-kafka.md "Tables in the test1 table" (the matcher is test1.*) "Tables in the test1 database"
ticdc/ticdc-sink-to-kafka.md "add the -enable-tls=true parameter to --sink-uri" enable-tls=true (the sink URI parameter table says enable-tls)
ticdc/ticdc-open-api.md "Query the replication task list" returns "the basic information of all nodes" "of all replication tasks"
ticdc/ticdc-csv.md TIME: "Format: yyyy-MM-dd" (the example is "23:59:59") HH:mm:ss
dm/dm-table-routing.md c-table, c-source c_table, c_source (as in the DDL)
dm/deploy-a-dm-cluster-using-tiup.md "when you deploy TiDB using TiUP" "when you deploy a DM cluster using TiUP"
dm/dm-export-import-config.md "## import the data source …" "## Import …" (as the Export heading)

The "Start downstream TiDB" commands in dm/quick-start-create-task.md also do not work, but fixing them needs a decision on the intended setup, so it is reported separately.

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.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)

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

  • Related code change PR links (if applicable):
  • This PR is translated from:
  • Other reference link(s):

AI agent involvement

  • The changes in this PR were primarily made by an AI agent on behalf of the PR author.

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

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Clarified that the TiUP guide covers deploying a DM cluster.
    • Corrected heading capitalization and table-routing examples, including downstream column names.
    • Updated the documented CSV TIME format to HH:mm:ss.
    • Clarified the replication task API’s returned information.
    • Corrected the Kafka TLS/SSL URI example and partition-dispatcher description.

…d DM docs

- ticdc-sink-to-kafka.md: "Tables in the `test1` table" → database (the
  matcher is `test1.*`), and the sink URI parameter is `enable-tls=true`,
  not `-enable-tls=true`.
- ticdc-open-api.md: the replication task list API returns replication
  tasks, not nodes.
- ticdc-csv.md: the `TIME` format is `HH:mm:ss` (the example is
  "23:59:59").
- dm-table-routing.md: use `c_table` and `c_source`, as the DDL does.
- deploy-a-dm-cluster-using-tiup.md: the note is about deploying a DM
  cluster, not TiDB.
- dm-export-import-config.md: capitalize the "Import" heading, as the
  "Export" heading is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ti-chi-bot

ti-chi-bot Bot commented Oct 19, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@ti-chi-bot ti-chi-bot Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 19, 2026
@coderabbitai

coderabbitai Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: pingcap/docs
  • Branch: master
  • File: .coderabbit.yaml
  • Commit: 3ba897a
  • Layers: Repository YAML
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 3e5db8a9-e747-438a-90da-0519f1ba068c
Commits

Reviewing files that changed from the base of the PR and between 1d6231b and 7fb5768.

Files selected for processing: 3
  • dm/task-configuration-file-full.md
  • migrate-small-mysql-shards-to-tidb.md
  • ticdc/ticdc-open-api.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

Walkthrough

This pull request updates DM and TiCDC documentation. It corrects deployment wording, capitalization, column names, a time format, an API description, and Kafka sink examples.

Changes: DM documentation

Layer / File(s) Summary
DM documentation corrections
dm/deploy-a-dm-cluster-using-tiup.md, dm/dm-export-import-config.md, dm/dm-table-routing.md, dm/task-configuration-file-full.md, migrate-small-mysql-shards-to-tidb.md
Clarified that the TiUP deployment note concerns a DM cluster, capitalized the “Import” heading, and corrected column names in table-routing guidance and configuration examples.

TiCDC documentation

Layer / File(s) Summary
TiCDC documentation corrections
ticdc/ticdc-csv.md, ticdc/ticdc-open-api.md, ticdc/ticdc-sink-to-kafka.md
Updated the documented TIME format to HH:mm:ss, corrected the replication task list API description, and corrected the TLS parameter and partition-dispatcher example description.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: qiancai

Merge Risk: Minimal · up to 7fb57

These documentation updates are mergeable; no current-head issue requiring remediation was found.

Architecture risk: Low · up to 1d623

The change affects 2 systems.

Changed systems: dm, ticdc

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — dm (service) was modified; 3 changed files map to changed impact.
  • observed — ticdc (service) was modified; 3 changed files map to changed impact.

Before / after behavior

  • observed — Modified behavior in dm/deploy-a-dm-cluster-using-tiup.md: Clarified that secret-key or interactive-password authentication applies when deploying a DM cluster with TiUP, replacing the previous TiDB deployment reference.
  • observed — Modified behavior in dm/dm-export-import-config.md: Capitalized the “Import” heading; the section content is otherwise unchanged.
  • observed — Modified behavior in dm/dm-table-routing.md: Corrected the column name in the warning from c-table to c_table.
  • observed — Modified behavior in dm/dm-table-routing.md: Corrected the column name in the warning from c-source to c_source.
Pre-merge checks: Passed 5
Check name Status Explanation
Description check Passed The description identifies all documentation corrections, affected versions, AI involvement, and unchanged related-file scope. The required sections are present and sufficiently complete.
Title check Passed The title clearly summarizes the main documentation fixes in the TiCDC and DM areas, including incorrect values, a parameter name, and identifiers.
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ti-chi-bot ti-chi-bot Bot added the missing-translation-status This PR does not have translation status info. label Oct 19, 2026
@ti-chi-bot ti-chi-bot Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 19, 2026
@yahonda
yahonda marked this pull request as ready for review October 20, 2026 00:12
@ti-chi-bot ti-chi-bot Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 20, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1


ℹ️ Review info
⚙️ Run configuration
  • Configuration used: Repository: pingcap/docs/.coderabbit.yaml
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 9c183b48-00bb-403e-94da-fd87b9c70594
📥 Commits

Reviewing files that changed from the base of the PR and between 3ba897a and 1d6231b.

📒 Files selected for processing: 6
  • dm/deploy-a-dm-cluster-using-tiup.md
  • dm/dm-export-import-config.md
  • dm/dm-table-routing.md
  • ticdc/ticdc-csv.md
  • ticdc/ticdc-open-api.md
  • ticdc/ticdc-sink-to-kafka.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 1 remain after this review.

Comment thread ticdc/ticdc-open-api.md Outdated
Without the `state` parameter, the API returns only the tasks in the
normal, stopped, or failed state, so "all replication tasks" is not
accurate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@qiancai qiancai added the translation/doing This PR's assignee is translating this PR. label Oct 27, 2026
@ti-chi-bot ti-chi-bot Bot removed the missing-translation-status This PR does not have translation status info. label Oct 27, 2026

@qiancai qiancai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Rest LGTM

Comment thread dm/dm-table-routing.md
> If any of the following errors occur, source information of sharded tables and schemas might fail to be written to the merged table.

- `c-table` is not in the last three columns:
- `c_table` is not in the last three columns:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

The same wrong identifier still exists in dm/task-configuration-file-full.md:65 — the comment there says "written to the c-table column of the merged table" while the YAML right below it correctly shows target-column: "c_table". Since this PR fixes c-table/c-source in this file, a follow-up fix in that sibling file would keep the docs consistent.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Thanks! Fixed in 7fb5768. The same c-table also appeared in the extract-table comment of migrate-small-mysql-shards-to-tidb.md:152, so I fixed it there too.

@ti-chi-bot ti-chi-bot Bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Oct 27, 2026
@ti-chi-bot

ti-chi-bot Bot commented Oct 27, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-10-27 13:54:34.734712335 +0000 UTC m=+469612.226424584: ☑️ agreed by qiancai.

@qiancai qiancai self-assigned this Oct 27, 2026
@qiancai qiancai added the needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. label Oct 27, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ti-chi-bot

ti-chi-bot Bot commented Oct 28, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from qiancai. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-1-more-lgtm Indicates a PR needs 1 more LGTM. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. translation/doing This PR's assignee is translating this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants