Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
ti-chi-bot
Bot
added
missing-translation-status
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (4)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthroughJapanese release notes from TiDB 6.0.0 DMR through 6.4.0 were edited for wording, terminology, links, and formatting. The 6.1.7 notes also gained entries describing a TiDB Lightning improvement and bug fixes. ChangesRelease-note revisions
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: 🔵 Low · up to The 6.4.0 release note retains an incorrect historical column name, which may mislead readers checking TiFlash replication progress. This is a localized documentation issue; the remaining summarized edits show no concrete additional mismatch. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
- Configuration used: Repository: pingcap/docs/.coderabbit.yaml
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
85da30f2-cb4f-4dc6-a927-9532b996019a
📒 Files selected for processing (12)
releases/release-6.0.0-dmr.mdreleases/release-6.1.0.mdreleases/release-6.1.1.mdreleases/release-6.1.2.mdreleases/release-6.1.3.mdreleases/release-6.1.4.mdreleases/release-6.1.5.mdreleases/release-6.1.6.mdreleases/release-6.1.7.mdreleases/release-6.2.0.mdreleases/release-6.3.0.mdreleases/release-6.4.0.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.
| - TiFlashデータ複製進捗状況の精度向上 [#4902](https://github.com/pingcap/tiflash/issues/4902) @[hehechen](https://github.com/hehechen) | ||
|
|
||
| TiDBでは、 `PROGRESS`テーブルの`INFORMATION_SCHEMA.TIFLASH_REPLICA`フィールドは、TiKVの対応するテーブルからTiFlashレプリカへのデータレプリケーションの進行状況をTiFlashために使用されます。以前のTiDBバージョンでは、 `PROCESS`フィールドは、 TiFlashレプリカの作成中のデータレプリケーションの進行状況のみを提供していました。TiFlashレプリカが作成された後、TiKVの対応するテーブルに新しいデータがインポートされた場合、このフィールドは更新されず、新しいデータのTiKVからTiFlashへのレプリケーションの進行状況は表示されません。 | ||
| TiDBでは、 `INFORMATION_SCHEMA.TIFLASH_REPLICA`テーブルの`PROGRESS`フィールドは、TiKVの対応するテーブルからTiFlashレプリカへのデータレプリケーションの進行状況を示すために使用されます。以前のTiDBバージョンでは、 `PROCESS`フィールドは、 TiFlashレプリカの作成中のデータレプリケーションの進行状況のみを提供していました。TiFlashレプリカが作成された後、TiKVの対応するテーブルに新しいデータがインポートされた場合、このフィールドは更新されず、新しいデータのTiKVからTiFlashへのレプリケーションの進行状況は表示されません。 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Correct the historical column name.
The TiDB v6.2.0 and v6.3.0 schemas use PROGRESS, not PROCESS, for this column. The upstream English release note repeats the typo, but this text should use the identifier in the schemas. (raw.githubusercontent.com)
TiDBでは、 `INFORMATION_SCHEMA.TIFLASH_REPLICA`テーブルの`PROGRESS`フィールドは、TiKVの対応するテーブルからTiFlashレプリカへのデータレプリケーションの進行状況を示すために使用されます。以前のTiDBバージョンでは、 `PROGRESS`フィールドは、 TiFlashレプリカの作成中のデータレプリケーションの進行状況のみを提供していました。TiFlashレプリカが作成された後、TiKVの対応するテーブルに新しいデータがインポートされた場合、このフィールドは更新されず、新しいデータのTiKVからTiFlashへのレプリケーションの進行状況は表示されません。
There was a problem hiding this comment.
Confirmed: the column is PROGRESS (TiDB v6.2.0 infoschema/tables.go), and the PROCESS typo comes from the EN source, which this line translates faithfully. I opened #24196 against release-8.5 to fix the EN text. The Japanese line will be updated by the weekly EN→JA sync after that PR is merged, so this PR keeps the current translation.
There was a problem hiding this comment.
@yahonda Thanks for clarifying the workflow. The PROGRESS correction is tracked in #24196. This PR can keep the current translation while the English fix and weekly EN→JA sync are pending.
✏️ Learnings added
Learnt from: yahonda
Repo: pingcap/docs PR: 24157
File: releases/release-6.4.0.md:162-162
Timestamp: 2026-10-06T06:45:54.340Z
Learning: In pingcap/docs, Japanese release notes on i18n-ja-release-8.5 receive a weekly EN→JA sync from release-8.5. Source-text errors can be corrected in the English release notes first, then propagated through that sync; a Japanese translation PR can retain the faithful translation while the upstream correction is pending.
Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.
You are interacting with an AI system.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 participant
What is changed, added or deleted? (Required)
Fixes translation defects in the Japanese release notes for v6.0.0-DMR to v6.4.0 (12 files). This is the first half of round 5 of the
releases/review; v6.5.x and v6.6.0 are in a separate PR. I checked each item against its EN bullet (release-8.5) and againstresources/terms-en-ja.md.Untranslated English
release-6.1.0.md: three paragraphs (L36ALTER TABLE ... COMPACT, L82LEADINGhint, L192 user-level locks), about 15 table cells, and the headings and link text that were still in English.release-6.1.1.mdtorelease-6.1.4.md: the H1, "Quick access", and section headings.Meaning fixes
3.2.0version and earlier" was rendered as "data earlier than 3.2.0".@[Reminiscent](6.1.2); a missing@(6.3.0).Glossary and literals
PARTITION BY RANGE COLUMNS (column_list),EXCHANGE PARTITION.feedback-probability,log-backup.enable,--no-confirm,mode,worker-count,row-error-delay,backup/import/cdc,enable-diagnostic,dttool migrate.@[hi-rustin], as in EN.Particles and Markdown
>, and backticks inside issue-link text.Not changed: the Data Migration component name (a separate pending term decision) and the order and spacing of handles.
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.
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
🤖 Generated with Claude Code
Summary by CodeRabbit