i18n(ja): unify optimizer katakana spelling (remove long vowel mark) - #23629
Open
yahonda wants to merge 3 commits into
Open
i18n(ja): unify optimizer katakana spelling (remove long vowel mark)#23629yahonda wants to merge 3 commits into
yahonda wants to merge 3 commits into
Conversation
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
Bot
added
missing-translation-status
📝 WalkthroughWalkthroughThe 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. ChangesJapanese optimizer terminology
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: 🟡 Moderate · up to 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: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation 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 checkExplanation 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 💡
🧪 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: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2f047154-6913-4fff-91ce-0d48b3c2dfff
📒 Files selected for processing (116)
TOC-tidb-cloud-essential.mdTOC-tidb-cloud-premium.mdTOC-tidb-cloud-starter.mdTOC-tidb-cloud.mdTOC.mdagg-distinct-optimization.mdanalyze-slow-queries.mdbenchmark/benchmark-tidb-using-ch.mdbenchmark/v4.0-performance-benchmarking-with-tpch.mdbest-practices/index-management-best-practices.mdbest-practices/multi-column-index-best-practices.mdcomment-syntax.mdcontrol-execution-plan.mdddl_embedded_analyze.mdderive-topn-from-window.mddevelop/dev-guide-hybrid-oltp-and-olap-queries.mddevelop/dev-guide-index-best-practice.mddevelop/dev-guide-join-tables.mdexplain-index-merge.mdexplain-indexes.mdexplain-joins.mdextended-statistics.mdfaq/sql-faq.mdfunctions-and-operators/tidb-functions.mdgenerated-columns.mdinformation-schema/information-schema-tiflash-replica.mdoptimizer-fix-controls.mdoptimizer-hints.mdquick-start-with-htap.mdreleases/release-1.0-ga.mdreleases/release-1.1-alpha.mdreleases/release-2.0-ga.mdreleases/release-2.0-rc.1.mdreleases/release-2.0.4.mdreleases/release-2.1-beta.mdreleases/release-2.1-ga.mdreleases/release-2.1-rc.1.mdreleases/release-2.1-rc.2.mdreleases/release-2.1-rc.3.mdreleases/release-2.1-rc.4.mdreleases/release-2.1-rc.5.mdreleases/release-2.1.1.mdreleases/release-2.1.16.mdreleases/release-2.1.17.mdreleases/release-2.1.18.mdreleases/release-2.1.19.mdreleases/release-2.1.3.mdreleases/release-2.1.4.mdreleases/release-2.1.5.mdreleases/release-2.1.6.mdreleases/release-3.0-beta.mdreleases/release-3.0-ga.mdreleases/release-3.0.0-beta.1.mdreleases/release-3.0.0-rc.1.mdreleases/release-3.0.0-rc.2.mdreleases/release-3.0.0-rc.3.mdreleases/release-3.0.2.mdreleases/release-3.0.3.mdreleases/release-3.0.4.mdreleases/release-3.0.5.mdreleases/release-3.0.6.mdreleases/release-3.0.8.mdreleases/release-3.1.0-beta.mdreleases/release-5.0.0-rc.mdreleases/release-6.1.0.mdreleases/release-6.1.1.mdreleases/release-6.3.0.mdreleases/release-6.4.0.mdreleases/release-6.5.0.mdreleases/release-6.5.10.mdreleases/release-6.6.0.mdreleases/release-7.0.0.mdreleases/release-7.1.0.mdreleases/release-7.1.6.mdreleases/release-7.2.0.mdreleases/release-7.4.0.mdreleases/release-7.5.3.mdreleases/release-7.6.0.mdreleases/release-8.0.0.mdreleases/release-8.1.1.mdreleases/release-8.4.0.mdreleases/release-pre-ga.mdreleases/release-rc.1.mdreleases/release-rc.2.mdreleases/release-rc.3.mdreleases/release-rc.4.mdsql-non-prepared-plan-cache.mdsql-physical-optimization.mdsql-plan-management.mdsql-plan-replayer.mdsql-prepared-plan-cache.mdsql-statements/sql-statement-alter-index.mdsql-statements/sql-statement-select.mdsql-statements/sql-statement-set-variable.mdsql-tuning-best-practice.mdsubquery-optimization.mdsystem-variable-reference.mdsystem-variables.mdtidb-cloud/releases/release-notes-2022.mdtidb-cloud/serverless-faqs.mdtidb-cloud/tidb-cloud-htap-quickstart.mdtidb-cloud/tidb-cloud-sql-tuning-overview.mdtidb-cloud/v6.5-performance-benchmarking-with-tpcc.mdtidb-cloud/v7.1-performance-benchmarking-with-tpcc.mdtidb-cloud/v7.5-performance-benchmarking-with-tpcc.mdtidb-cloud/v8.1-performance-benchmarking-with-tpcc.mdtidb-cloud/v8.5-performance-benchmarking-with-tpcc.mdtidb-performance-tuning-config.mdtiflash-performance-tuning-methods.mdtiflash/tiflash-late-materialization.mdtiflash/tiflash-overview.mdtiflash/tune-tiflash-performance.mdtiflash/use-tidb-to-read-tiflash.mdtiflash/use-tiflash-mpp-mode.mdtiup/tiup-bench.mdwrong-index-solution.md
Included review availability: Your plan provides up to 4 included reviews per hour; 0 remain after this review.
- 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.
qiancai
added
translation/no-need
…l-fix-optimizer-chouon-unification # Conflicts: # best-practices/multi-column-index-best-practices.md # explain-index-merge.md # optimizer-fix-controls.md # releases/release-7.2.0.md # releases/release-8.4.0.md
|
[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
size/XS
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)
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:
オプティマイザーafter the changeオプティマイザーー)クエリ オプティマイザ) confirmed pre-existing inupstream 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)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit
PLAN REPLAYER CAPTURE.