tidb-cloud: add the "TiDB X" term to glossary

[lilin90]

What is changed, added or deleted? (Required)

Add a new term "TiDB X"

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.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)

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

• This PR is translated from:
• Other reference link(s):
  • TiDB X: Introducing A New Foundation for Distributed SQL
  • PingCAP Launches TiDB X and New AI Capabilities

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

[gemini-code-assist]

Summary of Changes

Hello @lilin90, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the TiDB Cloud glossary by introducing a new key term, 'TiDB X', which describes an innovative distributed SQL architecture. Additionally, it refines an existing entry by clarifying 'Request Unit' with its common abbreviation '(RU)'. These changes aim to improve the documentation's accuracy and provide clearer definitions for important concepts within the TiDB Cloud ecosystem.

Highlights

• New Term: TiDB X: Introduced 'TiDB X' to the glossary, defining it as a new distributed SQL architecture leveraging cloud-native object storage for intelligent scaling, with links to relevant blog posts and press releases.
• Glossary Clarification: Updated the 'Request Unit' heading to 'Request Unit (RU)' for improved clarity and consistency within the glossary.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds the new term 'TiDB X' to the glossary and updates the 'Request Unit' heading to include its acronym 'RU'. The changes are good and improve the documentation's clarity and consistency. I've added one minor suggestion to make the description of 'TiDB X' more concise, in line with our style guide.

[lilin90]

Note for reviewers: We'll replace the links here with a coming link that points to an introduction about the TiDB X architecture.

[qiancai]

Rest LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-11-27 06:55:03.795861568 +0000 UTC m=+772267.445056025: ☑️ agreed by qiancai.

[dbsid]

lgtm

[ti-chi-bot]

@dbsid: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lilin90]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lilin90

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [lilin90]

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]

In response to a cherrypick label: new pull request created to branch master: #22129.
But this PR has conflicts, please resolve them!