i18n(ja): fix Cop task mistranslated as police officer - #23811
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe changes correct Japanese terminology and wording in a partitioned-tables best-practices guide and two release notes. No code or public entity declarations changed. ChangesDocumentation terminology corrections
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: Merge Risk: ⚪ Minimal · up to Japanese documentation now uses accurate Cop/COP task and kop terminology without changing product behavior or release-note meaning. No current merge-readiness risk remains. 🚥 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 |
|
[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 |
TiKV/TiFlash "Cop" (Coprocessor) tasks were mistranslated as the English homonym slang "cop" (police officer): 警官 (police officer) and 一部は タスクの収集 (task collection, a different misreading). Fixed to COP タスク / Cop タスク, matching the already-correct rendering used elsewhere in the same file (best-practices/ tidb-partitioned-tables-best-practices.md's own note: "COP タスクの メトリックは実行計画から派生します").
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
fa2d062 to
1e106a7
Compare
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
TiKV/TiFlash "Cop" (Coprocessor) tasks were mistranslated via the English homonym slang "cop" (police officer):
best-practices/tidb-partitioned-tables-best-practices.md's benchmark table header rendered EN "Cop tasks (index scan) / Cop tasks (table lookup) / Total Cop tasks" as "タスクの収集(インデックススキャン)/ 警官タスク(テーブル検索)/ 警官の合計タスク" (task collection / police officer task / police officer's total task), andreleases/release-6.5.1.mdrendered "the paging in a cop task" as "警官タスクのページング".Fixed to
COP タスク/Cop タスク, matching the already-correct rendering used elsewhere in the same best-practices file's own note: "COP タスクのメトリックは実行計画から派生します。"Found while independently re-reviewing PR #23810; kept as its own PR since it's an unrelated defect class (literal-identifier mistranslation, not partition-type naming).
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit