i18n(ja): unify the Japanese term for 'request' (part A of 2) - #23783
Merged
qiancai merged 6 commits intoSep 10, 2026
Merged
Conversation
ti-chi-bot
Bot
added
area/develop
|
[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
the
size/XXL
12 tasks
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
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 (2)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThis documentation-only change standardizes Japanese request terminology, revises selected wording, and converts dashboard metric labels to English. Release notes receive the same terminology updates. No product behavior or public declarations change. ChangesJapanese documentation terminology updates
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: 🔵 Low · up to This change standardizes Japanese request terminology and adjusts selected dashboard wording without changing product behavior. A small set of documentation descriptions remains inaccurate or inconsistent, which may confuse dashboard interpretation and privilege matching guidance, but presents bounded documentation risk. 🚥 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 |
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Sep 9, 2026
…shboard from this PR Both files fully overlapped with PR pingcap#23783/pingcap#23784 (the split halves of the 要求-to-リクエスト sweep, one of which had already fully restored grafana-performance-overview-dashboard.md's panel names). Since this branch was built from a pre-pingcap#23774 baseline, keeping these files here would revert that already-merged-in-spirit work and create a same-line merge conflict with pingcap#23783. The genuine new fixes from this PR (Raft apply/ready jargon, and the panel-name restoration for dashboard-monitoring.md that hadn't been done anywhere else) have been reapplied directly onto PR pingcap#23783's branch instead, so nothing is lost -- just moved to avoid duplicating/conflicting with already-in-flight work. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 15
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Advanced
Run ID: 2bd0d826-e0ec-40e0-9f4e-28e4e448cfee
📒 Files selected for processing (99)
alert-rules.mdauto-increment.mdbest-practices/best-practices-on-public-cloud.mdbest-practices/ddl-introduction.mdbest-practices/high-concurrency-best-practices.mdbest-practices/index-management-best-practices.mdbest-practices/pd-scheduling-best-practices.mdbest-practices/three-dc-local-read.mdbest-practices/three-nodes-hybrid-deployment.mdbr/backup-and-restore-use-cases.mdbr/br-checkpoint-backup.mdbr/br-log-architecture.mdbr/br-snapshot-architecture.mdcheck-before-deployment.mdcommand-line-flags-for-tidb-configuration.mdconfigure-load-base-split.mdcoprocessor-cache.mddashboard/dashboard-diagnostics-report.mddashboard/dashboard-diagnostics-usage.mddashboard/dashboard-metrics-relation.mddashboard/dashboard-monitoring.mddashboard/dashboard-ops-deploy.mddevelop/dev-guide-connection-parameters.mddevelop/dev-guide-get-data-from-single-table.mddevelop/dev-guide-use-follower-read.mddevelop/java-app-best-practices.mddm/dm-error-handling.mddm/dm-generate-self-signed-certificates.mddm/dm-open-api.mddm/feature-shard-merge-pessimistic.mddm/manually-handling-sharding-ddl-locks.mddr-solution-introduction.mddynamic-config.mderror-codes.mdexplain-partitions.mdfaq/deploy-and-maintain-faq.mdfollower-read.mdgenerate-self-signed-certificates.mdglobal-indexes.mdglossary.mdgrafana-overview-dashboard.mdgrafana-performance-overview-dashboard.mdgrafana-resource-control-dashboard.mdgrafana-tidb-dashboard.mdgrafana-tikv-dashboard.mdidentify-expensive-queries.mdidentify-slow-queries.mdinformation-schema/information-schema-cluster-log.mdinformation-schema/information-schema-inspection-result.mdinformation-schema/information-schema-metrics-summary.mdinformation-schema/information-schema-processlist.mdlatency-breakdown.mdmetrics-schema.mdmulti-data-centers-in-one-city-deployment.mdoptimistic-transaction.mdoptimizer-hints.mdpd-configuration-file.mdpd-control.mdperformance-tuning-methods.mdperformance-tuning-overview.mdperformance-tuning-practices.mdpessimistic-transaction.mdprivilege-management.mdreleases/release-2.1-ga.mdreleases/release-2.1-rc.1.mdreleases/release-2.1-rc.3.mdreleases/release-2.1.18.mdreleases/release-2.1.3.mdreleases/release-3.0-beta.mdreleases/release-3.0-ga.mdreleases/release-3.1.0-beta.2.mdreleases/release-3.1.0-ga.mdreleases/release-3.1.0-rc.mdreleases/release-3.1.1.mdreleases/release-4.0-ga.mdreleases/release-4.0.0-rc.1.mdreleases/release-4.0.0-rc.2.mdreleases/release-4.0.11.mdreleases/release-4.0.15.mdreleases/release-4.0.2.mdreleases/release-4.0.7.mdreleases/release-5.0.0-rc.mdreleases/release-5.0.6.mdreleases/release-5.1.0.mdreleases/release-5.1.1.mdreleases/release-5.1.2.mdreleases/release-5.1.4.mdreleases/release-5.1.5.mdreleases/release-5.2.0.mdreleases/release-5.2.2.mdreleases/release-5.2.4.mdreleases/release-5.3.0.mdreleases/release-5.3.3.mdreleases/release-5.4.0.mdreleases/release-5.4.3.mdreleases/release-6.0.0-dmr.mdreleases/release-6.1.1.mdreleases/release-6.1.2.mdreleases/release-6.2.0.md
Included review availability: Your plan provides up to 4 included reviews per hour; 0 remain after this review.
6 tasks
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Advanced
Run ID: a14045e6-ddc8-46c0-acbd-96082ed5cd54
📒 Files selected for processing (10)
configure-load-base-split.mddashboard/dashboard-monitoring.mddashboard/dashboard-ops-deploy.mddevelop/dev-guide-use-follower-read.mdgrafana-performance-overview-dashboard.mdgrafana-resource-control-dashboard.mdinformation-schema/information-schema-metrics-summary.mdperformance-tuning-methods.mdperformance-tuning-practices.mdreleases/release-4.0.0-rc.2.md
Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review.
qiancai
added
translation/no-need
Split from PR pingcap#23774 into two halves to stay under CodeRabbit's 150-file review limit (originally 197 files). See PR pingcap#23774 for the full context and review history -- both halves together are this same corpus-wide term-unification plus the incidental mistranslation fixes found while reviewing it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…nitoring doc, plus apply/ready jargon fixes Reconciled from a sibling branch (fix-raft-ready-apply-jargon) that independently found dashboard/dashboard-monitoring.md needed the same panel-name-English restoration as the grafana-*-dashboard.md campaign (never previously applied to this file), plus the Raft apply/ready literal-jargon fix already applied elsewhere in this campaign. Since that sibling branch was built from a pre-this-PR baseline, its version of this file (and grafana-performance-overview-dashboard.md, which this PR had already fully fixed) reverted this PR's own 要求-to-リクエスト conversions on a few lines -- re-applied those 4 corrections here so this file ends up with all three fixes (panel names, apply/ready jargon, and request conversions) simultaneously, avoiding a merge conflict with the sibling PR. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Reverting the earlier decision to keep Raft's 'apply' jargon as literal English in body-text descriptions (policy reversal, see pingcap#23781's latest commit for the full rationale). Restored to 適用 in the description text of dashboard/dashboard-monitoring.md and grafana-performance-overview-dashboard.md. Panel/metric LABELS (Apply Duration, Apply Log Duration headings) are unaffected -- those are the literal EN panel names, not the reverted word choice. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- grafana-resource-control-dashboard.md: removed a fabricated WRRU
abbreviation not present in EN.
- configure-load-base-split.md: restored 3 missing を particles before
超えます (all 3 sibling bullets in the same list had the same defect,
CodeRabbit flagged only 1).
- dashboard/dashboard-monitoring.md: restored missing を in the
tso-request/tso-cmd division sentence.
- dashboard/dashboard-ops-deploy.md: 再ネゴシエート (verb stem used as a
noun) -> 再ネゴシエーション (proper nominalized form).
- develop/dev-guide-use-follower-read.md: fixed a literal-but-backwards
rendering of EN's own awkward phrasing ('load the balance'), confirmed
via docs-cn's clearer 负载均衡 (load-balance) phrasing.
- grafana-performance-overview-dashboard.md: Sorter output events/s
bullet said the destination module is マウント (mount); the sibling
Mounter output events/s bullet calls the same module マウンター --
unified to マウンター.
- information-schema-metrics-summary.md: reworded 'coprocessor
requesting to queue up' to 'coprocessor request queuing up', matching
docs-cn's clearer 请求排队等待 phrasing (the cop REQUEST queues, the
coprocessor doesn't request the queuing).
- performance-tuning-methods.md: removed a redundant/contradictory
sentence that had the PD Client 'return TSFuture' twice (once
immediately, once after completion) -- docs-cn confirms the second
event is delivering the result INTO the already-returned TSFuture, not
a second return.
- performance-tuning-practices.md: fixed a duration/count category
error -- 28,000 is a count of tso cmd executions, not a duration; also
removed a stray counter word before 実行時間の合計.
- releases/release-4.0.0-rc.2.md: '指定された時間範囲をリクエスト' (request
the [already] specified time range) reworded to '時間範囲の指定をリクエスト'
(request that a time range be specified), matching the actual
behavior-change description (previously silent default, now errors
and asks the caller to specify a range).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… and PD scheduling sections
yahonda
force-pushed
the
fix-yokyu-to-request-part-a
branch
from
September 10, 2026 06:31
2162b07 to
33efbd7
Compare
qiancai
approved these changes
Sep 10, 2026
[LGTM Timeline notifier]Timeline:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is changed, added or deleted? (Required)
Split from PR #23774 into two halves (part A of 2) to stay under CodeRabbit's 150-file review limit (the original PR was 197 files, over the limit). See #23774 for the full context, method, and review history -- already fully reviewed via 6 parallel independent verification passes, all clean.
This half covers 99 files.
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