Skip to content

[fix](doc) fix typo in zh prefix-index sort-key advice (约 → 越)#3727

Merged
morningman merged 1 commit into
apache:masterfrom
boluor:fix-zh-prefix-index-typo
May 22, 2026
Merged

[fix](doc) fix typo in zh prefix-index sort-key advice (约 → 越)#3727
morningman merged 1 commit into
apache:masterfrom
boluor:fix-zh-prefix-index-typo

Conversation

@boluor
Copy link
Copy Markdown
Contributor

@boluor boluor commented May 22, 2026

Summary

The Chinese prefix-index page (table-design/index/prefix-index) gives advice on ordering Key columns by query frequency. The second bullet reads:

  1. 约常用的字段越放在前面,因为前缀索引只对 WHERE 条件中字段在 Key 的前缀中才有效。

The leading is a typo for — the sentence uses the 越……越…… ("the more … the more …") construction, so it should read:

  1. 越常用的字段越放在前面,因为前缀索引只对 WHERE 条件中字段在 Key 的前缀中才有效。

Reported in #3724.

Scope

The typo is present in the zh-CN 2.1 and 3.x docs. The 4.x / current Chinese page was rewritten and no longer contains this sentence, so no change is needed there.

Test plan

  • Confirmed the live 3.x and 2.1 zh pages still show 约常用的字段越放在前面, while the latest (4.x) page no longer has the sentence.
  • Dead-link check passes on the changed files.
  • CI build.

Closes #3724

The Chinese prefix-index page advises ordering Key columns by query
frequency. The second bullet read "约常用的字段越放在前面", where the
leading 约 is a typo for 越 — the sentence uses the "越……越……"
("the more … the more …") construction, so it should be
"越常用的字段越放在前面". Reported in apache#3724.

Present in the zh-CN 2.1 and 3.x docs; the 4.x/current Chinese page was
rewritten and no longer contains this sentence, so no change is needed there.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@boluor boluor mentioned this pull request May 22, 2026
@morningman morningman merged commit 02967d7 into apache:master May 22, 2026
3 checks passed
@boluor boluor deleted the fix-zh-prefix-index-typo branch May 22, 2026 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue on docs

2 participants