cloud: update limited SQL features for Premium#23012
Conversation
|
[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 |
There was a problem hiding this comment.
Code Review
This pull request updates the limited-sql-features.md file to document the SQL feature limitations and support status for the new TiDB Cloud Premium tier. The review feedback focuses on improving documentation clarity and technical accuracy, including correcting a table classification for metrics_schema, reducing repetition in the IMPORT INTO description, and simplifying the LOAD DATA INFILE entry by removing redundant phrasing.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| | `mysql` | `tidb` | Not supported [^4] | Not supported [^4] | | ||
| | Database | Table | TiDB Cloud Dedicated | TiDB Cloud Premium | {{{ .starter }}} and {{{ .essential }}} | | ||
| |:-|:-|:-|:-|:-| | ||
| | `metrics_schema` | All databases | / | Not supported | / | |
There was a problem hiding this comment.
In the Table column for the metrics_schema database, it should say All tables instead of All databases.
| | `metrics_schema` | All databases | / | Not supported | / | | |
| | `metrics_schema` | All tables | / | Not supported | / | |
References
- Ensure technical accuracy and terminology consistency by correcting mistakes. (link)
| | `CHANGE DRAINER` | Not supported [^7] | Not supported | Not supported [^7] | | ||
| | `CHANGE PUMP` | Not supported [^7] | Not supported | Not supported [^7] | | ||
| | `FLASHBACK CLUSTER` | Supported | Not supported | Not supported [^3] | | ||
| | `IMPORT INTO` | / | Blocks `IMPORT INTO` from a local file path. Blocks `IMPORT INTO` statements that use an S3 `EXTERNAL_ID`. | / | |
There was a problem hiding this comment.
To avoid unnecessary repetition of the phrase Blocks IMPORT INTO, we can combine the two sentences into a single, more concise sentence.
| | `IMPORT INTO` | / | Blocks `IMPORT INTO` from a local file path. Blocks `IMPORT INTO` statements that use an S3 `EXTERNAL_ID`. | / | | |
| | `IMPORT INTO` | / | Blocks `IMPORT INTO` from a local file path and statements that use an S3 `EXTERNAL_ID`. | / | |
References
- Avoid unnecessary words and repetition to improve clarity and readability. (link)
| | `CHANGE PUMP` | Not supported [^7] | Not supported | Not supported [^7] | | ||
| | `FLASHBACK CLUSTER` | Supported | Not supported | Not supported [^3] | | ||
| | `IMPORT INTO` | / | Blocks `IMPORT INTO` from a local file path. Blocks `IMPORT INTO` statements that use an S3 `EXTERNAL_ID`. | / | | ||
| | `LOAD DATA INFILE` | Supports `LOAD DATA LOCAL INFILE`, and `LOAD DATA INFILE` from Amazon S3 or Google Cloud Storage | Blocks `LOAD DATA LOCAL INFILE` from a local file path. | Only supports `LOAD DATA LOCAL INFILE` | |
There was a problem hiding this comment.
Since LOAD DATA LOCAL INFILE by definition only loads files from the client's local file system, adding from a local file path is redundant. We can simplify this to Blocks LOAD DATA LOCAL INFILE.
| | `LOAD DATA INFILE` | Supports `LOAD DATA LOCAL INFILE`, and `LOAD DATA INFILE` from Amazon S3 or Google Cloud Storage | Blocks `LOAD DATA LOCAL INFILE` from a local file path. | Only supports `LOAD DATA LOCAL INFILE` | | |
| | `LOAD DATA INFILE` | Supports `LOAD DATA LOCAL INFILE`, and `LOAD DATA INFILE` from Amazon S3 or Google Cloud Storage | Blocks `LOAD DATA LOCAL INFILE`. | Only supports `LOAD DATA LOCAL INFILE` | |
References
- Avoid unnecessary words and repetition to keep the documentation concise. (link)
…9546)
First-time contributors' checklist
What is changed, added or deleted? (Required)
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?