Skip to content

Conversation

@qiancai
Copy link
Collaborator

@qiancai qiancai commented Dec 10, 2025

What is changed, added or deleted? (Required)

Add a doc to introduce the feature support status for different TiDB Cloud plans, including TiDB Cloud Starter, TiDB Cloud Essential, and TiDB Cloud Dedicated.

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 the missing-translation-status This PR does not have translation status info. label Dec 10, 2025
@gemini-code-assist
Copy link

Summary of Changes

Hello @qiancai, 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 introduces a crucial new documentation page that clearly outlines the feature set available for each TiDB Cloud plan: Starter, Essential, and Dedicated. This addition aims to enhance user understanding of plan capabilities, ensuring they can easily identify which features are supported by their chosen tier. The corresponding navigation menus have also been refined to integrate this new resource seamlessly and improve overall clarity.

Highlights

  • New Features Documentation: A new document, tidb-cloud/features.md, has been added to provide a comprehensive overview of feature support across TiDB Cloud Starter, Essential, and Dedicated plans.
  • Table of Contents Updates: The Table of Contents files (TOC-tidb-cloud-essential.md, TOC-tidb-cloud-starter.md, TOC-tidb-cloud.md) have been updated to include a direct link to the newly added 'Features' document and to simplify the 'Get Started with TiDB Cloud' entry to 'Get Started'.
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.

@ti-chi-bot ti-chi-bot bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 10, 2025
Copy link

@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 introduces a new 'Features' documentation page that provides a clear comparison of feature availability across different TiDB Cloud plans. The changes also include updates to the table of contents in several files to link to this new page. My review focuses on improving the clarity and consistency of the new markdown file. I've suggested minor formatting adjustments to align with best practices, such as removing trailing whitespace, standardizing HTML tags, and ensuring the file ends with a newline.

<tr>
<td>Data Migration (using the TiDB Cloud console)<br></td>
<td>❌<br></td>
<td>✅ <br/>(Private preview)</td>

Choose a reason for hiding this comment

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

low

This file uses both <br> and <br/>. For consistency and to adhere to HTML5 standards, please use <br> throughout the document. This will improve readability and maintainability.

Suggested change
<td>✅ <br/>(Private preview)</td>
<td>✅ <br>(Private preview)</td>
References
  1. The style guide requires consistency. Using a single style for break tags improves readability and maintainability. (link)

github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Dec 10, 2025
github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Dec 10, 2025
@lilin90 lilin90 added the area/tidb-cloud This PR relates to the area of TiDB Cloud. label Dec 10, 2025
github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Dec 10, 2025
github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Dec 10, 2025
github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Dec 10, 2025
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 Dec 10, 2025
@ti-chi-bot
Copy link

ti-chi-bot bot commented Dec 10, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-12-10 09:52:26.495119943 +0000 UTC m=+1034691.308897525: ☑️ agreed by lilin90.

github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Dec 11, 2025
@likidu
Copy link
Collaborator

likidu commented Dec 11, 2025

And why some rows here have grey background versus
CleanShot 2025-12-11 at 09 26 48

Hi @likidu, the gray background is automatically applied by the global styles to all tables in the documentation website, so it is not added on purpose.

@qiancai Can we hard-coded the background color for the first column? As it looks a bit weird now and might raise some unnecessary confusions.

@qiancai
Copy link
Collaborator Author

qiancai commented Dec 11, 2025

I left a few comments in the PR, PTAL @lilin90 @qiancai

Also can we make the (Public preview) font smaller? As now it's cut as 2 lines: CleanShot 2025-12-11 at 09 25 10

Hi @likidu, thanks for the advice. I've changed the font size of words like public preview to show them in one line. Here is the latest doc preview link: https://pr.pingcap-docsite-preview.pages.dev/tidbcloud/features/

image

@ti-chi-bot ti-chi-bot bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Dec 11, 2025
github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Dec 11, 2025
@qiancai
Copy link
Collaborator Author

qiancai commented Dec 11, 2025

And why some rows here have grey background versus
CleanShot 2025-12-11 at 09 26 48

Hi @likidu, the gray background is automatically applied by the global styles to all tables in the documentation website, so it is not added on purpose.

@qiancai Can we hard-coded the background color for the first column? As it looks a bit weird now and might raise some unnecessary confusions.

Yes, here is the latest version with the background color hard-coded as white for the first column.
https://pr.pingcap-docsite-preview.pages.dev/tidbcloud/features/

image

github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Dec 11, 2025
github-actions bot pushed a commit to qiancai/pingcap-docsite-preview that referenced this pull request Dec 11, 2025
</tr>
<tr>
<td rowspan="7" style="background-color: white;">Security</td>
<td>Private endpoint</td>
Copy link
Member

Choose a reason for hiding this comment

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

Private Endpoint & VPC peering should belong to "Connection".
Connection:

  • Public Endpoint: all support
  • Private Endpoint: all suppport
  • VPC Peering: only Dedicated.

Copy link
Member

Choose a reason for hiding this comment

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

Private endpoint & VPC peering also belong to security, so it's reasonable to put them in Security, especially when we want to emphasize security.
image

Copy link
Member

Choose a reason for hiding this comment

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

@likidu Would you please also take a look?

@lilin90 lilin90 removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 12, 2025
@qiancai
Copy link
Collaborator Author

qiancai commented Dec 12, 2025

/approve

@qiancai qiancai added the lgtm label Dec 12, 2025
@ti-chi-bot
Copy link

ti-chi-bot bot commented Dec 12, 2025

[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

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

@ti-chi-bot ti-chi-bot bot added the approved label Dec 12, 2025
@ti-chi-bot ti-chi-bot bot merged commit 825533d into pingcap:release-8.5 Dec 12, 2025
9 checks passed
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 needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants