tidb-cloud: add the "TiDB X" term to glossary (#22095)#22129
tidb-cloud: add the "TiDB X" term to glossary (#22095)#22129ti-chi-bot wants to merge 1 commit intopingcap:masterfrom
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot
added
area/tidb-cloud
|
@lilin90 This PR has conflicts, I have hold it. |
|
@ti-chi-bot: ## If you want to know how to resolve it, please read the guide in TiDB Dev Guide. DetailsInstructions 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 ti-community-infra/tichi repository. |
|
[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 |
Summary of ChangesHello @ti-chi-bot, I'm Gemini Code Assist1! 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 primarily focuses on updating and expanding the TiDB Cloud documentation to reflect recent product developments. It introduces the new "TiDB X" distributed SQL architecture to the glossary and integrates detailed information about the Highlights
Using Gemini Code AssistThe 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
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 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
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds the new term "TiDB X" to the glossary and updates several related documents. While the intent is clear, multiple files contain unresolved merge conflict markers (<<<<<<<, =======, >>>>>>>). These must be resolved before merging, as they break the document rendering. I've left critical comments on each file where these markers appear. Additionally, I found a potential typo in the year mentioned in a link within the glossary.
| <<<<<<< HEAD | ||
|  | ||
| ======= | ||
| </CustomContent> | ||
|
|
||
| ## {{{ .starter }}} | ||
|
|
||
| {{{ .starter }}} is a fully managed, multi-tenant TiDB offering. It delivers an instant, autoscaling MySQL-compatible database. | ||
|
|
||
| The Starter cluster plan is ideal for those who are getting started with TiDB Cloud. It provides developers and small teams with the following features: | ||
|
|
||
| - **No cost**: This plan is completely free, with no credit card required to get started. | ||
| - **Storage**: Provides an initial 5 GiB of row-based storage and 5 GiB of columnar storage. | ||
| - **Request Units**: Includes 50 million [Request Units (RUs)](/tidb-cloud/tidb-cloud-glossary.md#request-unit-ru) for database operations. | ||
|
|
||
| ## {{{ .essential }}} | ||
|
|
||
| For applications experiencing growing workloads and needing scalability in real time, the Essential cluster plan provides the flexibility and performance to keep pace with your business growth with the following features: | ||
|
|
||
| - **Enhanced capabilities**: includes all capabilities of the Starter plan, along with the capacity to handle larger and more complex workloads, as well as advanced security features. | ||
| - **Automatic scaling**: automatically adjusts storage and computing resources to efficiently meet changing workload demands. | ||
| - **High availability**: built-in fault tolerance and redundancy ensure your applications remain available and resilient, even during infrastructure failures. | ||
| - **Predictable pricing**: billed based on storage and Request Capacity Units (RCUs) of the compute resources, offering transparent, usage-based pricing that scales with your needs, so you only pay for what you use without surprises. | ||
|
|
||
| {{{ .essential }}} offers two types of high availability to address varying operational requirements. | ||
|
|
||
| - By default, clusters utilizing the Zonal High Availability option have all components located within the same availability zone, which results in lower network latency. | ||
| - For applications that require maximum infrastructure isolation and redundancy, the Regional High Availability option distributes nodes across multiple availability zones. | ||
|
|
||
| For more information, see [High Availability in {{{ .starter }}} and Essential](/tidb-cloud/serverless-high-availability.md). | ||
| >>>>>>> 604ed60c95 (tidb-cloud: add the "TiDB X" term to glossary (#22095)) |
There was a problem hiding this comment.
This section contains unresolved merge conflict markers (<<<<<<< HEAD, =======, >>>>>>>). These markers must be removed to ensure the document renders correctly. Please resolve the conflict and keep only the intended content for this file.
| <<<<<<< HEAD | ||
| The serverless driver itself is free, but accessing data with the driver generates [Request Units (RUs)](/tidb-cloud/tidb-cloud-glossary.md#request-unit) and storage usage. The pricing follows the [TiDB Cloud Serverless pricing](https://www.pingcap.com/tidb-serverless-pricing-details/) model. | ||
| ======= | ||
| The serverless driver itself is free, but accessing data with the driver generates [Request Units (RUs)](/tidb-cloud/tidb-cloud-glossary.md#request-unit-ru) and storage usage. | ||
|
|
||
| - For {{{ .starter }}} clusters, the pricing follows the [{{{ .starter }}} pricing](https://www.pingcap.com/tidb-cloud-starter-pricing-details/) model. | ||
| - For {{{ .essential }}} clusters, the pricing follows the [{{{ .essential }}} pricing](https://www.pingcap.com/tidb-cloud-essential-pricing-details/) model. | ||
| >>>>>>> 604ed60c95 (tidb-cloud: add the "TiDB X" term to glossary (#22095)) |
There was a problem hiding this comment.
Unresolved merge conflict markers are present in the Pricing section. Please remove the markers (<<<<<<< HEAD, =======, >>>>>>>) and the duplicated content to fix the document.
| <<<<<<< HEAD | ||
| Some of TiDB Cloud features are partially supported or not supported on TiDB Cloud Serverless. For more information, see [TiDB Cloud Serverless Limitations and Quotas](/tidb-cloud/serverless-limitations.md). | ||
| ======= | ||
| - A fully managed database with both row-based and columnar storage, ideal for hybrid OLTP and OLAP workloads. | ||
| - Automatic and request-driven scaling, no capacity planning or manual tuning required. | ||
| - Built-in vector search and full-text search to power GenAI retrieval, chatbots, and other AI applications. | ||
| - Always-free monthly quota for up to five clusters per organization (5 GiB row data + 5 GiB columnar data + 50 million [RUs](/tidb-cloud/tidb-cloud-glossary.md#request-unit-ru) per cluster). | ||
| >>>>>>> 604ed60c95 (tidb-cloud: add the "TiDB X" term to glossary (#22095)) |
There was a problem hiding this comment.
This section contains unresolved merge conflict markers. Please resolve the conflict by removing the markers and ensuring the correct answer to the question is present.
| <<<<<<< HEAD | ||
| TiDB Cloud Serverless adopts a pay-as-you-go model, meaning that you only pay for the storage space and cluster usage. In this model, all cluster activities such as SQL queries, bulk operations, and background jobs are quantified in [Request Units (RUs)](/tidb-cloud/tidb-cloud-glossary.md#request-unit). RU is an abstract measurement for the size and intricacy of requests initiated on your cluster. For more information, see [TiDB Cloud Serverless Pricing Details](https://www.pingcap.com/tidb-cloud-serverless-pricing-details/). | ||
| ======= | ||
| {{{ .starter }}} adopts a pay-as-you-go model, meaning that you only pay for the storage space and cluster usage. In this model, all cluster activities such as SQL queries, bulk operations, and background jobs are quantified in [Request Units (RUs)](/tidb-cloud/tidb-cloud-glossary.md#request-unit-ru). RU is an abstract measurement for the size and intricacy of requests initiated on your cluster. For more information, see [{{{ .starter }}} Pricing Details](https://www.pingcap.com/tidb-cloud-starter-pricing-details/). | ||
| >>>>>>> 604ed60c95 (tidb-cloud: add the "TiDB X" term to glossary (#22095)) |
There was a problem hiding this comment.
This section contains unresolved merge conflict markers. Please resolve the conflict to ensure the content is displayed correctly.
|
|
||
| A new distributed SQL architecture that makes cloud-native object storage the backbone of TiDB. By decoupling compute and storage, TiDB X enables TiDB to scale intelligently, adapting in real time to workload patterns, business cycles, and data characteristics. | ||
|
|
||
| The TiDB X architecture is now available in <CustomContent plan="starter,essential">{{{ .starter }}} and Essential</CustomContent><CustomContent plan="premium">{{{ .starter }}}, Essential, and Premium</CustomContent>. For more information, see [Introducing TiDB X: A New Foundation for Distributed SQL in the Era of AI](https://www.pingcap.com/blog/introducing-tidb-x-a-new-foundation-distributed-sql-ai-era/) and [PingCAP Launches TiDB X and New AI Capabilities at SCaiLE Summit 2025](https://www.pingcap.com/press-release/pingcap-launches-tidb-x-new-ai-capabilities/). |
There was a problem hiding this comment.
The link text mentions "SCaiLE Summit 2025", which appears to be a future date. Given the context of the announcement, this might be a typo. Please verify if the year should be 2024 or if it should be removed to avoid confusion.
| The TiDB X architecture is now available in <CustomContent plan="starter,essential">{{{ .starter }}} and Essential</CustomContent><CustomContent plan="premium">{{{ .starter }}}, Essential, and Premium</CustomContent>. For more information, see [Introducing TiDB X: A New Foundation for Distributed SQL in the Era of AI](https://www.pingcap.com/blog/introducing-tidb-x-a-new-foundation-distributed-sql-ai-era/) and [PingCAP Launches TiDB X and New AI Capabilities at SCaiLE Summit 2025](https://www.pingcap.com/press-release/pingcap-launches-tidb-x-new-ai-capabilities/). | |
| The TiDB X architecture is now available in <CustomContent plan="starter,essential">{{{ .starter }}} and Essential</CustomContent><CustomContent plan="premium">{{{ .starter }}}, Essential, and Premium</CustomContent>. For more information, see [Introducing TiDB X: A New Foundation for Distributed SQL in the Era of AI](https://www.pingcap.com/blog/introducing-tidb-x-a-new-foundation-distributed-sql-ai-era/) and [PingCAP Launches TiDB X and New AI Capabilities at SCaiLE Summit](https://www.pingcap.com/press-release/pingcap-launches-tidb-x-new-ai-capabilities/). |
|
@ti-chi-bot: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
Since this PR only made changes to the |
2 participants
This is an automated cherry-pick of #22095
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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?