Skip to content

Conversation

@lilyjazz
Copy link
Member

@lilyjazz lilyjazz commented Jan 11, 2026

First-time contributors' checklist

What is changed, added or deleted? (Required)

Optimize the comparison between 3 tiers.

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):

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

@ti-chi-bot ti-chi-bot bot added missing-translation-status This PR does not have translation status info. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 11, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @lilyjazz, 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 refines the documentation for TiDB Cloud features by optimizing the comparison across its three tiers. The changes include introducing new symbols for feature status, reorganizing feature categories, renaming several features for enhanced clarity, and updating the availability status and descriptions for various functionalities. The aim is to provide a more accurate, detailed, and user-friendly overview of the features available in different TiDB Cloud plans.

Highlights

  • Enhanced Feature Status Legend: Introduced new symbols 🔒 for 'Private preview' and 🚧 for 'Under development' to provide more granular status for features. The symbol's description was also updated to include 'public preview'.
  • Comprehensive Table Reorganization: The feature comparison table has undergone significant restructuring, including the creation of new categories such as 'Develop friendly' and 'Network connection', and the reordering of existing features for better logical grouping.
  • Feature Renaming and Clarification: Several features were renamed for improved clarity and precision, including 'TiKV' to 'Scalable Transaction Processing', 'TiFlash' to 'Analytical Processing', 'Maintenance window' to 'System maintenance window', and 'Recycle bin' to 'Backup file recycle bin'.
  • Addition of New Features: New feature entries have been added to the comparison, such as 'Vector storage & search', 'Data branch', 'SQL editor', 'Scale with workload', 'Manual modify cluster', 'Data export via CSV, Parquet, and SQL files to local or object storages', 'Changefeed allows you to replicate change data to Kafka or other MySQL-compatible databases', and 'Public endpoint'.
  • Updates to Feature Availability and Descriptions: The availability status for 'Data migration' and 'Database audit logging' was updated to 'Private preview' (🔒) for specific tiers, and 'Alerting' status was changed to 'Under development' (🚧). Descriptions for 'Third-party integrations' and 'IAM' were also expanded.
  • Removal of Obsolete Entries: The 'Recovery group (cross-region)' and 'Standard storage' entries were removed from the feature list, streamlining the documentation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request optimizes the feature descriptions in the TiDB Cloud feature comparison table, making them more descriptive and reorganizing them into more logical categories. The changes significantly improve clarity for users. I've provided several suggestions to fix typos, improve grammar, and ensure consistent terminology and phrasing throughout the document, aligning with the repository's style guide.

</tr>
<tr>
<td rowspan="6" style="background-color: white;">Cluster management</td>
<td>Scale with workload</td>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

To maintain consistency with other documentation, such as select-cluster-tier.md which uses "Automatic scaling", I suggest changing "Scale with workload" to "Automatic scaling".

Suggested change
<td>Scale with workload</td>
<td>Automatic scaling</td>

lilyjazz and others added 2 commits January 11, 2026 15:54
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@lilyjazz lilyjazz changed the title optimze the description of TIDX-X features. optimze the description of TiDB-X features. Jan 11, 2026
github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Jan 12, 2026
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@qiancai qiancai self-assigned this Jan 12, 2026
@qiancai qiancai added the translation/no-need No need to translate this PR. label Jan 12, 2026
@ti-chi-bot ti-chi-bot bot removed the missing-translation-status This PR does not have translation status info. label Jan 12, 2026
@qiancai qiancai added missing-translation-status This PR does not have translation status info. area/tidb-cloud This PR relates to the area of TiDB Cloud. labels Jan 12, 2026
@lilin90 lilin90 removed the missing-translation-status This PR does not have translation status info. label Jan 12, 2026
@lilin90 lilin90 changed the title optimze the description of TiDB-X features. Optimize the description of TiDB-X features Jan 12, 2026
@lilin90 lilin90 requested a review from likidu January 12, 2026 03:07
Co-authored-by: Lilian Lee <lilin@pingcap.com>
@likidu
Copy link
Collaborator

likidu commented Jan 12, 2026

LTGM!

Copy link
Member

@lilin90 lilin90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Jan 13, 2026
@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jan 13, 2026
@ti-chi-bot
Copy link

ti-chi-bot bot commented Jan 13, 2026

[LGTM Timeline notifier]

Timeline:

  • 2026-01-13 03:35:30.309987405 +0000 UTC m=+328574.371852313: ☑️ agreed by lilin90.
  • 2026-01-13 03:36:34.143893218 +0000 UTC m=+328638.205758137: ☑️ agreed by qiancai.

@qiancai qiancai changed the title Optimize the description of TiDB-X features cloud: optimize the description of TiDB-X features Jan 13, 2026
@qiancai qiancai added the type/enhancement The issue or PR belongs to an enhancement. label Jan 13, 2026
@qiancai
Copy link
Collaborator

qiancai commented Jan 13, 2026

/approve

@ti-chi-bot ti-chi-bot bot added the approved label Jan 13, 2026
@qiancai qiancai added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 13, 2026
@qiancai
Copy link
Collaborator

qiancai commented Jan 13, 2026

/approve

@ti-chi-bot
Copy link

ti-chi-bot bot commented Jan 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

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:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@qiancai qiancai removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 13, 2026
@ti-chi-bot ti-chi-bot bot merged commit d8952be into release-8.5 Jan 13, 2026
9 checks passed
breezewish added a commit that referenced this pull request Jan 13, 2026
* origin/release-8.5: (48 commits)
  Terraform: remove `cluster_id` in `cluster_id, vpc_peering_id` (#22318)
  Update the Compatibility changes of release-8.5.4 (#22233) (#22316)
  cloud: optimize the description of TiDB-X features (#22294)
  Add FORMAT keyword to import statement options (#22301) (#22304)
  cloud: delete disaster recovery (#22299)
  v8.5.4 tikv: update default settings of `server.grpc-concurrency` and `server.grpc-raft-conn-num`. (#22273) (#22298)
  Update create-tidb-instance-premium.md (#22288)
  sync-diff-inspector: add PROCESS permission when upstream and downstream are TiDB (#22289) (#22292)
  sql-faq: fix outdated description about JDBC (#22283) (#22287)
  master, v8.5: update download URL from pingcap.org to pingcap.com (#22240) (#22280)
  tikv: fix the default value of `end-point-memory-quota` (#22271) (#22272)
  v8.5.4: tikv: update auto compaction config (#22251) (#22265)
  pdf: update year to 2026 in copyright.tex (#22253) (#22260)
  v8.5.4 tikv: update rocksdb.max-manifest-file-size default value (#21689) (#22250)
  tidb-cloud: update the RU definition (#22197)
  cloud: update backup policies and execution rules (#22227)
  cloud: add release notes for 20251230 (#22247)
  cloud: add private link connection docs for overview and Confluent (#22246)
  tiproxy: add tiproxy usage in the tidb cloud doc (#21483)
  cloud: update the retention note for the latest automatic backup (#22248)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved area/tidb-cloud This PR relates to the area of TiDB Cloud. lgtm size/L Denotes a PR that changes 100-499 lines, ignoring generated files. translation/no-need No need to translate this PR. type/enhancement The issue or PR belongs to an enhancement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants