Repository navigation
i18n(ja): use one rendering for compaction in the release notes (part 2) - #24258
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
[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 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (48)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughRelease notes across TiDB versions replace compression terminology with compaction terminology in Japanese descriptions. The edits preserve the documented settings, conditions, and behavior. ChangesCompaction terminology updates
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This PR updates Japanese release-note terminology without changing product behavior. No concrete user-facing or operational regression is supported, so it appears ready to merge after normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 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 |
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
Renders "compaction" (RocksDB, TiKV, TiFlash, and log backup compaction) as コンパクション instead of 圧縮 in the release notes. This is part 2 of the change in #24200, which covered the reference docs. 圧縮 is the established Japanese word for "compression", so using it for compaction made release notes such as 「圧縮率を自動的に調整」 (EN "adjusts the compaction rate") read as if they were about data compression.
This PR changes 92 lines in 48 files.
How each site was chosen
releases/was matched with its EN line onrelease-8.5.Wording changes beyond the plain replacement
releases/release-5.0.0-rc.md: 「圧縮率」 (EN "compaction rate", meaning speed) → 「コンパクション速度」. A plain replacement would be 「コンパクション率」, which reads like "compression ratio". The same feature's heading inrelease-5.0.0.mduses 「データコンパクション速度」.releases/release-8.5.5.md: 「圧縮ログバックアップ」 (EN "compacted log backups") → 「コンパクションされたログバックアップ」.Kept as 圧縮 because EN says "compress" or "compression" (78 lines)
These include gRPC message compression, Dumpling and TiDB Lightning compression formats, zstd and lz4, TiFlash
dt_compression_*, redo log compression, the MySQL compression protocol, andUNCOMPRESS(). Therelease-5.0.0.mdheading 「TiFlashは、圧縮とデータソートにおけるI/Oリソースの使用を制限します」 is also kept, because EN says "compression and data sorting".Configuration names, anchors, and code are unchanged.
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