Repository navigation
i18n(ja): fix TiDB Cloud Lake docs, part 2 of 4 (SQL reference a-d) - #24441
Merged
qiancai merged 16 commits intoOct 14, 2026
Merged
Conversation
Use one term for aggregate functions, the aggregating index, and SQL aggregation in general, which matches other databases' Japanese docs and the rest of the TiDB Japanese docs. Keep the other term where the text means combining values into one array, JSON value, or geometry, and where the English is not "aggregate". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…iDB Cloud Lake docs Translate the "Step N", "Tutorial N", and "Example-N" labels left in English in headings, using the forms that the rest of the Japanese docs use, and unify the one file that used a different word for "Step". Fully translate the few example headings left in English. Translate the "Scenario:" label in the CityDrive guides. Heading anchors are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…TiDB Cloud Lake docs Translate the titles of the function category pages and the integration task pages that were left in English, matching their sibling pages that are already translated. Update the link texts that repeat these titles. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Translate the titles of feature overview pages whose Japanese term is already used in the page body or in sibling pages (indexes, masking policy, stored procedure, stream, tag, table, external function, EXPLAIN commands, and Information_Schema tables). Keep engine and table-format names, Full-Text Index, and Stage in English. Update the TOC labels and link texts that repeat these titles. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- _index.md: move the "Corresponding EN commit" comment below the front matter. With the comment on line 1, the front matter was not parsed and the page rendered it as body text with an empty title. - Delete guides/ai-powered-features.md and guides/manage-costs.md, and drop the billing role section from guides/roles.md, to match the English docs (pingcap#24422). The translation sync does not carry over file deletions. - Remove links and bold markup that were added to front matter summaries. Summaries are plain text. - Restore the list markers in three notes, so that each item renders as a separate bullet, and move a sentence back to its original item. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… docs The custom anchors in the Japanese headings collapsed double hyphens and changed underscores to hyphens (for example, create-table-like instead of create-table--like, and record-delimiter instead of record_delimiter). Links copied from the English docs use the English slugs, so 38 links in the Japanese Lake docs did not resolve. Set each custom anchor to the slug that the English heading produces, including the -1 suffix for repeated headings. All in-page and cross-page anchor links in the Lake docs now resolve. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fix sentences whose Japanese meaning differs from the English, each checked against the English source. Examples: - NULL handling in GET, GET_PATH, GET_IGNORE_CASE, JSON_EXTRACT_PATH_TEXT, SHA, XXHASH32, and XXHASH64: the value is returned as the type, and NULL is returned only for NULL input. - "exclusive" bounds were rendered as "mutually exclusive". - The "occurrence" argument of REGEXP_INSTR and REGEXP_SUBSTR is an ordinal, not a count. - "Sets or unsets a setting" was rendered as enable or disable. - "surface area", "candidate", the "View" permission, the "Spec." (specifier) column, "data warehouse", and "extra load" were rendered with the wrong sense. - A network policy limits the source IP ranges of connections, not the destination. - Restore Apache Iceberg and geometry type names that must stay literal. - Fix broken Japanese, stray spaces, and a doubled "see" phrase. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d Lake docs Translate headings, table header cells, bold prose labels, and page titles that were left in English, and update the link texts that repeat them. Heading anchors are unchanged. Keep in English: identifiers (system.* and information_schema.* tables, option names, data type names), object and feature names (Stage, Warehouse, Worksheets, Fail-Safe, Schema Evolution, and so on), UI field names, data source names, and the admonition labels that the site renders. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Translate ordinary English words and phrases left in the prose of the Lake guides and tutorials, such as integration task, primary key, snapshot, security group, sandbox, role, policy, dataset, and link texts that repeat translated page titles. Translate the Yes/No values in the "Required" columns. Remove the stray space in the Japanese term for row access policy. Keep identifiers, UI labels, feature names, and terms that the translation glossary keeps in English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…erence Translate ordinary English words and phrases left in the prose of the Lake SQL reference pages, such as bitmap, snapshot, timestamp, specifier, policy, user, table, link texts that repeat translated page titles, month and weekday names in descriptions, and the "Global" object type value. Keep identifiers, SQL keywords, function and type names, and terms that the translation glossary keeps in English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Skipping CI for Draft Pull Request. |
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
📝 Walkthrough
Merge Risk: 🔵 Low · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly identifies a Japanese localization fix for the TiDB Cloud Lake SQL reference documentation and specifies the covered file range. |
| Description check | |
The description is complete and relevant. It explains the scope, change themes, affected version, related references, AI involvement, and applicable change categories. The optional translated-from fie… |
| Docstring Coverage | |
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 | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches: 💡 1
-
🛠️ Fix failing CI checks: 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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 help to get the list of available commands.
ti-chi-bot
Bot
added
the
missing-translation-status
|
[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
…e SQL reference Use the term that the AWS Japanese docs and the rest of the TiDB Japanese docs use for "external ID" in prose. Parameter names stay in English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d time functions page Match the other tables on the same page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The dictionary pages used two Japanese terms for "dictionary". Use the one that the dictionary overview page and the DDL overview use. The page title and link text "Dictionary" stay in English as an object name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Translate "select expression", "search expression", and "result expression", which were left in English in the prose. The argument names stay in English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… page Match the same sentence in the SHOW CREATE DICTIONARY page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…DE page Follow up on the previous commit, which left spaces between Japanese words. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yahonda
marked this pull request as ready for review
October 14, 2026 02:21
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to GitHub limitations.
🟡 Minor · Cloudflare R2 リンクを修正してください。 · create-stage.md:173
tidb-cloud-lake/sql/create-stage.md:173
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winCloudflare R2 リンクを修正してください。
提示されたリンクチェックでは、このリンク先が 404 を返しています。リンク先を公式 R2 ドキュメントに変更してください。Cloudflare の現行 R2 ドキュメントはこちらです。(developers.cloudflare.com)
Proposed wording: リンク先を
https://developers.cloudflare.com/r2/に変更します。As per path instructions, flag “Broken or stale links in user-facing documentation.”
Sources: Path instructions, Pipeline failures
🟡 Minor · Align the DATE_BETWEEN summary with its reference page. · date-time-functions.md:61
tidb-cloud-lake/sql/date-time-functions.md:61
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick winAlign the
DATE_BETWEENsummary with its reference page.The linked page documents
DATE_BETWEEN(unit, start, end)as returning an integer. This row instead documents a three-date Boolean predicate. If the Boolean form is supported, document both forms in the reference page. Otherwise, replace this row with the documented contract.🐛 Suggested fix
-| [DATE_BETWEEN](/tidb-cloud-lake/sql/date-between.md) | ある日付が他の 2 つの日付の間にあるかを確認します | `DATE_BETWEEN('2024-06-04', '2024-06-01', '2024-06-10')` → `true` | +| [DATE_BETWEEN](/tidb-cloud-lake/sql/date-between.md) | 2 つの日付または timestamp の間隔を指定した単位で整数として返します | `DATE_BETWEEN(DAY, '2024-06-01', '2024-06-04')` → `3` |
ℹ️ Review info
⚙️ Run configuration
- Configuration used: Repository: pingcap/docs/.coderabbit.yaml
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
f3cb30d2-babf-433e-beeb-9c39465c43dc
📒 Files selected for processing: 99
tidb-cloud-lake/sql/add-months.mdtidb-cloud-lake/sql/aggregating-index-sql.mdtidb-cloud-lake/sql/alter-database.mdtidb-cloud-lake/sql/alter-notification-integration.mdtidb-cloud-lake/sql/alter-table.mdtidb-cloud-lake/sql/alter-user.mdtidb-cloud-lake/sql/alter-warehouse-unassign-nodes.mdtidb-cloud-lake/sql/alter-warehouse.mdtidb-cloud-lake/sql/alter-worker.mdtidb-cloud-lake/sql/alter-workload-group.mdtidb-cloud-lake/sql/any-value.mdtidb-cloud-lake/sql/apache-icebergtm-tables.mdtidb-cloud-lake/sql/array-aggregate.mdtidb-cloud-lake/sql/array-filter.mdtidb-cloud-lake/sql/array-functions.mdtidb-cloud-lake/sql/array-generate-range.mdtidb-cloud-lake/sql/array-indexof.mdtidb-cloud-lake/sql/array-slice.mdtidb-cloud-lake/sql/at.mdtidb-cloud-lake/sql/avg-if.mdtidb-cloud-lake/sql/avg.mdtidb-cloud-lake/sql/begin.mdtidb-cloud-lake/sql/bitmap-functions.mdtidb-cloud-lake/sql/bitmap-has-all.mdtidb-cloud-lake/sql/bitmap-has-any.mdtidb-cloud-lake/sql/bitmap-intersect.mdtidb-cloud-lake/sql/bitmap-not-count.mdtidb-cloud-lake/sql/bitmap-or-count.mdtidb-cloud-lake/sql/bitmap-subset-in-range.mdtidb-cloud-lake/sql/bitmap-union.mdtidb-cloud-lake/sql/bitmap-xor-count.mdtidb-cloud-lake/sql/bitmap.mdtidb-cloud-lake/sql/catalog.mdtidb-cloud-lake/sql/changes.mdtidb-cloud-lake/sql/clause.mdtidb-cloud-lake/sql/connection-parameters.mdtidb-cloud-lake/sql/connection.mdtidb-cloud-lake/sql/context-functions.mdtidb-cloud-lake/sql/convert-timezone.mdtidb-cloud-lake/sql/copy-into-location.mdtidb-cloud-lake/sql/copy-into-table.mdtidb-cloud-lake/sql/cosine-distance.mdtidb-cloud-lake/sql/count-distinct.mdtidb-cloud-lake/sql/count-if.mdtidb-cloud-lake/sql/count.mdtidb-cloud-lake/sql/covar-samp.mdtidb-cloud-lake/sql/create-aggregate-function.mdtidb-cloud-lake/sql/create-aggregating-index.mdtidb-cloud-lake/sql/create-connection.mdtidb-cloud-lake/sql/create-database.mdtidb-cloud-lake/sql/create-dictionary.mdtidb-cloud-lake/sql/create-external-table.mdtidb-cloud-lake/sql/create-function.mdtidb-cloud-lake/sql/create-inverted-index.mdtidb-cloud-lake/sql/create-masking-policy.mdtidb-cloud-lake/sql/create-notification-integration.mdtidb-cloud-lake/sql/create-password-policy.mdtidb-cloud-lake/sql/create-procedure.mdtidb-cloud-lake/sql/create-role.mdtidb-cloud-lake/sql/create-row-access-policy.mdtidb-cloud-lake/sql/create-scalar-function.mdtidb-cloud-lake/sql/create-sequence.mdtidb-cloud-lake/sql/create-spatial-index.mdtidb-cloud-lake/sql/create-stage.mdtidb-cloud-lake/sql/create-stream.mdtidb-cloud-lake/sql/create-table.mdtidb-cloud-lake/sql/create-tag.mdtidb-cloud-lake/sql/create-task.mdtidb-cloud-lake/sql/create-temp-table.mdtidb-cloud-lake/sql/create-vector-index.mdtidb-cloud-lake/sql/create-warehouse.mdtidb-cloud-lake/sql/create-workload-group.mdtidb-cloud-lake/sql/data-anonymization-functions.mdtidb-cloud-lake/sql/data-types.mdtidb-cloud-lake/sql/date-add.mdtidb-cloud-lake/sql/date-between.mdtidb-cloud-lake/sql/date-diff.mdtidb-cloud-lake/sql/date-time-functions.mdtidb-cloud-lake/sql/date-time.mdtidb-cloud-lake/sql/days.mdtidb-cloud-lake/sql/ddl-database-overview.mdtidb-cloud-lake/sql/ddl-table-overview.mdtidb-cloud-lake/sql/ddl.mdtidb-cloud-lake/sql/decades.mdtidb-cloud-lake/sql/decode.mdtidb-cloud-lake/sql/delete.mdtidb-cloud-lake/sql/delta-lake-engine.mdtidb-cloud-lake/sql/desc-connection.mdtidb-cloud-lake/sql/desc-masking-policy.mdtidb-cloud-lake/sql/desc-row-access-policy.mdtidb-cloud-lake/sql/desc-sequence.mdtidb-cloud-lake/sql/desc-stage.mdtidb-cloud-lake/sql/describe-pipe.mdtidb-cloud-lake/sql/dml.mdtidb-cloud-lake/sql/drop-aggregating-index.mdtidb-cloud-lake/sql/drop-inverted-index.mdtidb-cloud-lake/sql/drop-masking-policy.mdtidb-cloud-lake/sql/drop-row-access-policy.mdtidb-cloud-lake/sql/drop-table.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.
This was referenced Oct 14, 2026
ti-chi-bot
Bot
removed
the
missing-translation-status
qiancai
approved these changes
Oct 14, 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)
This PR is part 2 of 4 that fix the Japanese TiDB Cloud Lake docs (
tidb-cloud-lake/, added in #24373 and synced in #24431). The changes come from a full review of all 1,121 Japanese Lake files against the English source onrelease-8.5. Following the request to group related fixes, the fixes are filed as four PRs that do not touch the same files. Each PR keeps one commit per theme, so you can review it commit by commit.This PR covers
tidb-cloud-lake/sql/files whose names start with a to d (98 files).Commits (themes):
Kept in English on purpose: identifiers, SQL keywords, function and type names, UI labels, the admonition labels that the site renders, and the terms that
resources/terms-en-ja.mdkeeps in English (stage, Warehouse, Worksheet, Schema Evolution, and so on). The "ロード (load)" gloss is kept because the glossary requires it.Related: the glossary entry
Aggregation → 集計is removed in #24438 so that the translator can choose the term from context.Other parts of this series: #24440, #24442, #24443
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