Skip to content

i18n(ja): unify optimizer katakana spelling (remove long vowel mark) - #23629

Open
yahonda wants to merge 2 commits into
i18n-ja-release-8.5from
fix-optimizer-chouon-unification
Open

i18n(ja): unify optimizer katakana spelling (remove long vowel mark)#23629
yahonda wants to merge 2 commits into
i18n-ja-release-8.5from
fix-optimizer-chouon-unification

Conversation

@yahonda

@yahonda yahonda commented Aug 27, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Unifies the katakana spelling of "optimizer" (オプティマイザー → オプティマイザ, removing the long
vowel mark) corpus-wide. Direction decided previously: オプティマイザ (no ー) matches the dominant
form and optimizer-hints.md's own H1. Fresh recount confirms: 592 no-vowel vs 259 with-vowel
(~70/30 majority for no-vowel).

Mechanical substring replace (オプティマイザー is unambiguous, no other meaning), verified:

  • 0 remaining オプティマイザー after the change
  • 0 double-vowel artifacts (オプティマイザーー)
  • markdownlint clean on all 116 changed files
  • no number-counter-spacing regressions
  • katakana-space instances found nearby (e.g. クエリ オプティマイザ) confirmed pre-existing in
    upstream before this change, unrelated to this substitution — left untouched (out of scope)

116 files, 259 occurrences.

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

  • i18n-ja-release-8.5 (TiDB Japanese documentation for TiDB 8.5 versions)

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

  • 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

Summary by CodeRabbit

  • Documentation
    • Standardized Japanese optimizer terminology across guides, references, FAQs, benchmarks, and release notes.
    • Updated related table-of-contents and cross-reference labels while preserving existing links.
    • Clarified the description of optimizer information captured by PLAN REPLAYER CAPTURE.
    • Corrected a release-note spelling inconsistency and improved formatting in one troubleshooting guide.
    • No product behavior, procedures, or technical content was changed.

Direction decided 2026-07-24/08-04: オプティマイザ (no ー) matches
the dominant corpus form and optimizer-hints.md's own H1. Fresh
recount: 592 no-vowel vs 259 with-vowel (~70/30). Mechanical
substring replace, verified 0 remaining オプティマイザー and no
double-vowel artifacts. 116 files, 259 occurrences.
@ti-chi-bot

ti-chi-bot Bot commented Aug 27, 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 assign tangenta 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:

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

@ti-chi-bot ti-chi-bot Bot added missing-translation-status This PR does not have translation status info. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. area/develop This PR relates to the area of TiDB App development. labels Aug 27, 2026
@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The pull request standardizes Japanese optimizer terminology across table-of-contents entries, guides, references, TiDB Cloud documentation, TiFlash documentation, and historical release notes. Links, procedures, examples, and technical content remain unchanged.

Changes

Japanese optimizer terminology

Layer / File(s) Summary
Core documentation and navigation
TOC*.md, *.md, best-practices/*, develop/*, sql-statements/*, tiflash/*
Japanese references to オプティマイザー and related terms now use オプティマイザ. Optimizer fix-control link targets remain unchanged.
Release notes
releases/*
Historical Japanese release notes use the standardized optimizer spelling. One heading changes from オプティマイザ to オプティマイザー.
TiDB Cloud and benchmark documentation
tidb-cloud/*, benchmark/*, tiup/*
Japanese optimizer terminology was normalized in workload guides, benchmark procedures, FAQs, and TiFlash descriptions. No procedural content changed.

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

Merge Risk: 🟡 Moderate · up to f396e

The documentation update still contains one duplicated term that renders incorrectly and one inconsistent optimizer spelling, so the Japanese content is not fully correct or consistently unified. Fix these localized issues before merging.

Suggested reviewers: qiancai, invalid-email-address

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.
Title check ✅ Passed The title clearly summarizes the main change: standardizing Japanese optimizer katakana spelling by removing the long vowel mark.
Description check ✅ Passed The description completes the required change summary and version sections. It also records validation results, AI involvement, and scope decisions. Optional reference links remain blank, but the desc…
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (116 skipped: 116 unsupported.)

Full details: Description check

Explanation

The description completes the required change summary and version sections. It also records validation results, AI involvement, and scope decisions. Optional reference links remain blank, but the description is sufficiently complete.

✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix-optimizer-chouon-unification

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.

@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: 2


ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2f047154-6913-4fff-91ce-0d48b3c2dfff

📥 Commits

Reviewing files that changed from the base of the PR and between a349332 and f396e69.

📒 Files selected for processing (116)
  • TOC-tidb-cloud-essential.md
  • TOC-tidb-cloud-premium.md
  • TOC-tidb-cloud-starter.md
  • TOC-tidb-cloud.md
  • TOC.md
  • agg-distinct-optimization.md
  • analyze-slow-queries.md
  • benchmark/benchmark-tidb-using-ch.md
  • benchmark/v4.0-performance-benchmarking-with-tpch.md
  • best-practices/index-management-best-practices.md
  • best-practices/multi-column-index-best-practices.md
  • comment-syntax.md
  • control-execution-plan.md
  • ddl_embedded_analyze.md
  • derive-topn-from-window.md
  • develop/dev-guide-hybrid-oltp-and-olap-queries.md
  • develop/dev-guide-index-best-practice.md
  • develop/dev-guide-join-tables.md
  • explain-index-merge.md
  • explain-indexes.md
  • explain-joins.md
  • extended-statistics.md
  • faq/sql-faq.md
  • functions-and-operators/tidb-functions.md
  • generated-columns.md
  • information-schema/information-schema-tiflash-replica.md
  • optimizer-fix-controls.md
  • optimizer-hints.md
  • quick-start-with-htap.md
  • releases/release-1.0-ga.md
  • releases/release-1.1-alpha.md
  • releases/release-2.0-ga.md
  • releases/release-2.0-rc.1.md
  • releases/release-2.0.4.md
  • releases/release-2.1-beta.md
  • releases/release-2.1-ga.md
  • releases/release-2.1-rc.1.md
  • releases/release-2.1-rc.2.md
  • releases/release-2.1-rc.3.md
  • releases/release-2.1-rc.4.md
  • releases/release-2.1-rc.5.md
  • releases/release-2.1.1.md
  • releases/release-2.1.16.md
  • releases/release-2.1.17.md
  • releases/release-2.1.18.md
  • releases/release-2.1.19.md
  • releases/release-2.1.3.md
  • releases/release-2.1.4.md
  • releases/release-2.1.5.md
  • releases/release-2.1.6.md
  • releases/release-3.0-beta.md
  • releases/release-3.0-ga.md
  • releases/release-3.0.0-beta.1.md
  • releases/release-3.0.0-rc.1.md
  • releases/release-3.0.0-rc.2.md
  • releases/release-3.0.0-rc.3.md
  • releases/release-3.0.2.md
  • releases/release-3.0.3.md
  • releases/release-3.0.4.md
  • releases/release-3.0.5.md
  • releases/release-3.0.6.md
  • releases/release-3.0.8.md
  • releases/release-3.1.0-beta.md
  • releases/release-5.0.0-rc.md
  • releases/release-6.1.0.md
  • releases/release-6.1.1.md
  • releases/release-6.3.0.md
  • releases/release-6.4.0.md
  • releases/release-6.5.0.md
  • releases/release-6.5.10.md
  • releases/release-6.6.0.md
  • releases/release-7.0.0.md
  • releases/release-7.1.0.md
  • releases/release-7.1.6.md
  • releases/release-7.2.0.md
  • releases/release-7.4.0.md
  • releases/release-7.5.3.md
  • releases/release-7.6.0.md
  • releases/release-8.0.0.md
  • releases/release-8.1.1.md
  • releases/release-8.4.0.md
  • releases/release-pre-ga.md
  • releases/release-rc.1.md
  • releases/release-rc.2.md
  • releases/release-rc.3.md
  • releases/release-rc.4.md
  • sql-non-prepared-plan-cache.md
  • sql-physical-optimization.md
  • sql-plan-management.md
  • sql-plan-replayer.md
  • sql-prepared-plan-cache.md
  • sql-statements/sql-statement-alter-index.md
  • sql-statements/sql-statement-select.md
  • sql-statements/sql-statement-set-variable.md
  • sql-tuning-best-practice.md
  • subquery-optimization.md
  • system-variable-reference.md
  • system-variables.md
  • tidb-cloud/releases/release-notes-2022.md
  • tidb-cloud/serverless-faqs.md
  • tidb-cloud/tidb-cloud-htap-quickstart.md
  • tidb-cloud/tidb-cloud-sql-tuning-overview.md
  • tidb-cloud/v6.5-performance-benchmarking-with-tpcc.md
  • tidb-cloud/v7.1-performance-benchmarking-with-tpcc.md
  • tidb-cloud/v7.5-performance-benchmarking-with-tpcc.md
  • tidb-cloud/v8.1-performance-benchmarking-with-tpcc.md
  • tidb-cloud/v8.5-performance-benchmarking-with-tpcc.md
  • tidb-performance-tuning-config.md
  • tiflash-performance-tuning-methods.md
  • tiflash/tiflash-late-materialization.md
  • tiflash/tiflash-overview.md
  • tiflash/tune-tiflash-performance.md
  • tiflash/use-tidb-to-read-tiflash.md
  • tiflash/use-tiflash-mpp-mode.md
  • tiup/tiup-bench.md
  • wrong-index-solution.md

Included review availability: Your plan provides up to 4 included reviews per hour; 0 remain after this review.

Comment thread releases/release-7.2.0.md Outdated
Comment thread subquery-optimization.md
- releases/release-7.2.0.md: remove a stray dangling text fragment
  before a link.
- agg-distinct-optimization.md: restore a missing opening backtick
  around distinct (matching the code-span convention already used
  elsewhere in the same file), and fix a clause-ordering mistranslation
  that misattributed "for aggregate functions" to the wrong DISTINCT
  form.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/develop This PR relates to the area of TiDB App development. missing-translation-status This PR does not have translation status info. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant