i18n-ja-release-8.5: translate doc changes from pingcap/docs release-8.5 on 2026-10-01

[github-actions]

What is changed, added or deleted? (Required)

Translate documentation changes from pingcap/docs release-8.5 to Japanese via ai-markdown-translator commit-diff sync.

English commit diff:

e9461de...49ed15d

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

• i18n-ja-release-8.5

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

• Source repo: pingcap/docs
• Source branch: release-8.5
• TOCs: TOC.md,TOC-ai.md,TOC-api.md,TOC-best-practices.md,TOC-develop.md,TOC-tidb-releases.md,TOC-tidb-cloud.md,TOC-tidb-cloud-starter.md,TOC-tidb-cloud-essential.md,TOC-tidb-cloud-premium.md,TOC-tidb-cloud-releases.md
• Source files: TOC-tidb-cloud-essential.md,TOC-tidb-cloud-premium.md,TOC-tidb-cloud-releases.md,TOC-tidb-cloud.md,TOC.md,ai/ti/guides/ti-git-workspace-for-agents-example.md,ai/ti/reference/ti-fs-copy-file.md,ai/ti/reference/ti-fs-create-hardlink.md,ai/ti/reference/ti-fs-create-layer.md,ai/ti/reference/ti-fs-delete-file-system-token.md,ai/ti/reference/ti-fs-delete-file.md,ai/ti/reference/ti-fs-describe-file.md,ai/ti/reference/ti-fs-disable-file-system-token.md,ai/ti/reference/ti-fs-enable-file-system-token.md,ai/ti/reference/ti-fs-list-file-system-tokens.md,ai/ti/reference/ti-fs-mount-file-system.md,ai/ti/reference/ti-fs-pack-file-system.md,ai/ti/ti-quick-start.md,best-practices/haproxy-best-practices.md,best-practices/tidb-best-practices.md,br/backup-and-restore-storages.md,clinic/clinic-user-guide-for-tiup.md,constraints.md,dashboard/dashboard-diagnostics-report.md,develop/dev-guide-join-tables.md,dm/dm-best-practices.md,dm/dm-faq.md,encryption-at-rest.md,filter-binlog-event.md,functions-and-operators/tidb-functions.md,information-schema/information-schema-data-lock-waits.md,information-schema/information-schema-deadlocks.md,information-schema/information-schema-tidb-trx.md,literal-values.md,metrics-schema.md,migrate-with-more-columns-downstream.md,performance-tuning-practices.md,releases/release-4.0.16.md,releases/release-5.0.6.md,releases/release-5.1.5.md,releases/release-5.2.0.md,releases/release-5.2.2.md,releases/release-5.3.0.md,releases/release-5.3.2.md,releases/release-5.4.3.md,releases/release-6.1.0.md,releases/release-6.5.7.md,releases/release-6.6.0.md,releases/release-7.1.4.md,releases/release-7.5.1.md,sql-mode.md,sql-statements/sql-statement-admin-show-ddl.md,sql-statements/sql-statement-admin.md,sql-statements/sql-statement-calibrate-resource.md,sql-statements/sql-statement-commit.md,sql-statements/sql-statement-create-database.md,sql-statements/sql-statement-create-index.md,sql-statements/sql-statement-create-sequence.md,sql-statements/sql-statement-create-user.md,sql-statements/sql-statement-distribute-table.md,sql-statements/sql-statement-drop-binding.md,sql-statements/sql-statement-drop-placement-policy.md,sql-statements/sql-statement-explain-analyze.md,sql-statements/sql-statement-grant-role.md,sql-statements/sql-statement-modify-column.md,sql-statements/sql-statement-overview.md,sql-statements/sql-statement-rename-table.md,sql-statements/sql-statement-select.md,sql-statements/sql-statement-set-resource-group.md,sql-statements/sql-statement-show-analyze-status.md,sql-statements/sql-statement-show-bindings.md,sql-statements/sql-statement-show-create-resource-group.md,sql-statements/sql-statement-show-grants.md,sql-statements/sql-statement-show-placement.md,sql-statements/sql-statement-show-stats-buckets.md,sql-statements/sql-statement-show-stats-histograms.md,sql-statements/sql-statement-shutdown.md,sql-statements/sql-statement-split-region.md,statistics.md,tidb-cloud/branch-manage.md,tidb-cloud/changefeed-overview.md,tidb-cloud/changefeed-sink-to-apache-kafka.md,tidb-cloud/changefeed-sink-to-apache-pulsar.md,tidb-cloud/changefeed-sink-to-cloud-storage.md,tidb-cloud/changefeed-sink-to-mysql.md,tidb-cloud/changefeed-sink-to-tidb-cloud.md,tidb-cloud/configure-external-storage-access.md,tidb-cloud/data-pipeline-configure-external-stage-alibaba-cloud.md,tidb-cloud/data-pipeline-configure-external-stage-aws.md,tidb-cloud/data-pipeline-dedicated-sink-to-lake.md,tidb-cloud/data-pipeline-essential-sink-to-lake.md,tidb-cloud/data-pipeline-lake-faq.md,tidb-cloud/data-pipeline-lake-sql-compatibility.md,tidb-cloud/data-pipeline-sink-to-lake.md,tidb-cloud/data-pipeline.md,tidb-cloud/data-service-api-key.md,tidb-cloud/data-service-manage-endpoint.md,tidb-cloud/data-service-manage-github-connection.md,tidb-cloud/data-service-oas-with-nextjs.md,tidb-cloud/essential-changefeed-sink-to-kafka.md,tidb-cloud/essential-changefeed-sink-to-mysql.md,tidb-cloud/monitor-built-in-alerting.md,tidb-cloud/premium/import-csv-files-premium.md,tidb-cloud/premium/import-from-s3-premium.md,tidb-cloud/premium/tidb-cloud-auditing-premium.md,tidb-cloud/releases/_index.md,tidb-cloud/releases/tidb-cloud-kernel-versioning.md,tidb-cloud/releases/tidb-cloud-release-notes.md,tidb-cloud/releases/tidb-x-cloud.202603.1.md,tidb-cloud/set-up-private-endpoint-connections.md,tidb-cloud/stream-data-overview.md,tidb-cloud/tidb-cloud-billing.md,tidb-cloud/tiered-storage-faq.md,tidb-cloud/tiered-storage-guide.md,tidb-cloud/tiered-storage-limitations.md,tidb-cloud/tiered-storage-observability.md,tidb-cloud/tiered-storage-overview.md,tidb-lightning/monitor-tidb-lightning.md,tidb-troubleshooting-map.md
• Source files translation mode: incremental
• Sync outcome: failure

Partial or incomplete translations

The following files contain useful generated output, but still require review or retry.

• tidb-cloud/data-pipeline-lake-sql-compatibility.md: Markdown table 2 repair rejected: repair changed protected uppercase identifiers; Markdown table 9 repair rejected: repair changed protected numbers; Markdown table 2 remains suspicious after repair: entire table is unchanged from the source; Markdown table 5 remains suspicious after repair: 2 natural-language body row(s) are unchanged from the source; Markdown table 9 remains suspicious after repair: table header is unchanged from the source

Translation failures

The following files were not translated automatically and must be handled manually before merging.

• tidb-cloud/tidb-cloud-billing.md: AI translation failed or returned invalid results

Docs with document structure mismatches after translation

The following files were translated, but their Markdown heading or CustomContent structure does not match the source HEAD file.

• TOC-tidb-cloud-premium.md: expected heading anchors are missing
  • Source: build-allowlist
  • Target: (no stable headings)
  • First difference: expected anchor {#build-allowlist} is missing from target
• tidb-cloud/set-up-private-endpoint-connections.md: heading level sequence differs
  • Source: #x1 ##x3 ###x6 ##x1 ###x2 ##x1 ###x2 ##x1 ###x1
  • Target: #x1 ##x3 ###x6 ##x1 ###x2 ##x1 ###x1 ##x1 ###x2
  • First difference: heading 16: source ###, target ##
• tidb-cloud/set-up-private-endpoint-connections.md: stable heading relative order differs
  • Source: restrictions -> prerequisites -> set-up-a-private-endpoint-connection-and-connect-to-your-cluster -> step-1-select-a-tidb-cluster -> step-2-create-an-aws-interface-endpoint -> step-3-create-a-private-endpoint-connection -> step-4-enable-private-dns -> step-5-connect-to-your-tidb-cluster -> ... (+9 more)
  • Target: restrictions -> prerequisites -> set-up-a-private-endpoint-connection-and-connect-to-your-cluster -> step-1-select-a-tidb-cluster -> step-2-create-an-aws-interface-endpoint -> step-3-create-a-private-endpoint-connection -> step-4-enable-private-dns -> step-5-connect-to-your-tidb-cluster -> ... (+9 more)
  • First difference: stable heading 15: source step-2-create-a-cross-region-aws-interface-endpoint, target troubleshooting

Before merging this PR, manually translate the failed files above or rerun this workflow with translation_scope set to 'Translate only specified files' and file_names set to those paths.

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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: pingcap/docs/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 15707943-2c72-4116-b021-98ec998f044f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[ti-chi-bot]

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[yahonda]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yahonda
Once this PR has been reviewed and has the lgtm label, please assign lance6716 for approval. 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:

• OWNERS

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