You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove documentation for Chat2Query, which has been removed from the TiDB Cloud console, and its API, which is being retired.
Delete the Chat2Query API, knowledge base, and multi-round session guides; remove related steps, concepts, examples, navigation entries, and references.
Retain manual SQL Editor documentation under explore-data-with-sql-editor.md, update inbound links, and redirect all four removed page URLs using aliases.
Remove the retired SQL Editor feature for generating a Data Service endpoint from a SQL file and its cross-reference.
Preserve historical release note entries and remove only obsolete documentation references.
Validation: scoped Markdownlint and internal link checks (25 files), plus git diff --check.
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.
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 ti-community-infra/tichi repository.
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign lance6716 for approval. For more information see the Code Review Process. Please ensure that each of them provides their approval before proceeding.
The full list of commands accepted by this bot can be found here.
Details
Needs approval from an approver in each of these files:
The documentation adds a SQL Editor preview guide and updates related links and instructions. It removes Chat2Query API guides and references from Data Service and other pages. The release notes add TiDB Cloud updates dated April 28 through October 20, 2026.
Adds SQL Editor preview instructions for access, query execution, SQL files, and settings. The quickstart now demonstrates direct SQL entry. Related links point to the SQL Editor guide. Conflict markers appear in the cluster connection and quickstart content.
Data Service and Chat2Query API documentation tidb-cloud/data-service-*, tidb-cloud/use-chat2query-*
Removes Chat2Query API, knowledge, and sessions guides. Data Service pages no longer describe Chat2Query endpoints, AI-generated SQL, or Chat2Data response examples.
Product references and navigation TOC-tidb-cloud*.md, tidb-cloud/ai-feature-concepts.md, tidb-cloud/tidb-cloud-glossary.md, tidb-cloud/tidb-cloud-roadmap.md, tidb-cloud/releases/release-notes-2023.md, tidb-cloud/releases/release-notes-2024.md
Updates SQL Editor navigation labels and removes Chat2Query references from concept, glossary, roadmap, and older release-note content.
2026 TiDB Cloud release notes
Layer / File(s)
Summary
October release notes tidb-cloud/releases/tidb-cloud-release-notes.md
Adds October notes about Chat2Query support ending, integrations, previews, public endpoint defaults, BYOC alerts, capacity modes, and manual backups.
September and late-August release notes tidb-cloud/releases/tidb-cloud-release-notes.md
This documentation change cannot merge as is. Conflict markers would be published in several TiDB Cloud pages and navigation files, and the release notes carry about 700 lines of unrelated entries with broken links. The retired Chat2Query page and its links also remain. Resolve the conflicts, trim the release notes to the intended change, and fix the remaining links before merging.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title clearly and concisely identifies the main change: removing Chat2Query documentation from TiDB Cloud.
Description check
The description is mostly complete. It explains the documentation removals, retained SQL Editor documentation, aliases, affected version, validation steps, AI involvement, and deleted files.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within survi…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (19 skipped: 19 unsupported.)
Finishing Touches: 💡 1
🛠️ Fix failing CI checks: 💡
Commit to this branch
Create a new PR
🧪 Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
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. I understand the commands that are listed here.
Remove the retained Chat2Query page and its stale references.
The page remains reachable from both TiDB Cloud TOCs, but it links to the deleted Chat2Query API page and the missing #chat2query glossary anchor. It also documents retired Chat2Query and endpoint-generation features. Delete tidb-cloud/explore-data-with-chat2query.md, update both TOCs to link to explore-data-with-sql-editor.md, and remove the retired Chat2Query references from ai-feature-concepts.md instead of patching the deleted-page link.
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
1. Create a table in your {{{ .starter }}} instance.
You can use [SQL Editor in the TiDB Cloud console](https://docs.pingcap.com/tidbcloud/explore-data-with-chat2query) to execute SQL statements. Here is an example:
You can use [SQL Editor in the TiDB Cloud console](https://docs.pingcap.com/tidbcloud/explore-data-with-sql-editor) to execute SQL statements. Here is an example:
The reason will be displayed to describe this comment to others. Learn more.
Major · Functional Correctness · Quick win
Use repository-relative links for the new SQL Editor page.
The absolute URL returns 404 in the changed-line link check because this page is introduced in the same change and is not yet deployed. Replace both links with /tidb-cloud/explore-data-with-sql-editor.md.
Proposed wording for both occurrences:You can use [SQL Editor in the TiDB Cloud console](/tidb-cloud/explore-data-with-sql-editor.md) to execute SQL statements. Here is an example:
1. Create a table in your {{{ .starter }}} instance and insert some data.
You can use [SQL Editor in the TiDB Cloud console](https://docs.pingcap.com/tidbcloud/explore-data-with-chat2query) to execute SQL statements. Here is an example:
You can use [SQL Editor in the TiDB Cloud console](https://docs.pingcap.com/tidbcloud/explore-data-with-sql-editor) to execute SQL statements. Here is an example:
The reason will be displayed to describe this comment to others. Learn more.
Major · Functional Correctness · Quick win
Use repository-relative links for the new SQL Editor page.
The absolute URL returns 404 in the changed-line link check because this page is introduced in the same change and is not yet deployed. Replace both links with /tidb-cloud/explore-data-with-sql-editor.md.
Proposed wording for both occurrences:You can use [SQL Editor in the TiDB Cloud console](/tidb-cloud/explore-data-with-sql-editor.md) to execute SQL statements. Here is an example:
Chat2Query is an AI-powered feature integrated into SQL Editor that assists users in generating, debugging, or rewriting SQL queries using natural language instructions. For more information, see [Explore your data with AI-assisted SQL Editor](/tidb-cloud/explore-data-with-chat2query.md).
In addition, TiDB Cloud provides a Chat2Query API for {{{ .starter }}} instances. After it is enabled, TiDB Cloud will automatically create a system Data App called Chat2Query and a Chat2Data endpoint in Data Service. You can call this endpoint to let AI generate and execute SQL statements by providing instructions. For more information, see [Get started with Chat2Query API](/tidb-cloud/use-chat2query-api.md).
The reason will be displayed to describe this comment to others. Learn more.
Major · Functional Correctness · Quick win
Remove the unresolved Chat2Query conflict block.
The file still contains merge markers and the retired /tidb-cloud/use-chat2query-api.md link. Internal-link CI reports this link as invalid. Markdownlint also reports missing blank lines around the conflict-generated headings.
## Vector search (PREVIEW)
Tools
markdownlint-cli2 (0.23.3)
[warning] 13-13: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Above
(MD022, blanks-around-headings)
[warning] 19-19: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 21-21: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Above
(MD022, blanks-around-headings)
[warning] 21-21: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
In SQL Editor, you can write and run SQL queries. This enables you to run SQL queries against databases without a local SQL client. You can intuitively view the query results in tables or charts and easily check the query logs.
The reason will be displayed to describe this comment to others. Learn more.
Major · Functional Correctness · Quick win
Resolve the remaining merge conflict in the SQL Editor paragraph.
The file still retains <<<<<<< HEAD, =======, and >>>>>>> plus the old Chat2Query sentence at line 48. This leaves a dead #chat2query link and exposes obsolete instructions. Keep the SQL Editor-only paragraph and remove the conflict markers and Chat2Query sentence.
> TiDB Cloud provides a Chat2Query API for {{{ .starter }}} instances. After it is enabled, TiDB Cloud will automatically create a system Data App called **Chat2Query** and a Chat2Data endpoint in Data Service. You can call this endpoint to let AI generate and execute SQL statements by providing instructions.
>
> For more information, see [Get started with Chat2Query API](/tidb-cloud/use-chat2query-api.md).
This document introduces how to quickly get started with TiDB Cloud Data Service (beta) by creating a Data App, developing, testing, deploying, and calling an endpoint. A Data App is a collection of endpoints that you can use to access data for a specific application.
=======
This document introduces how to quickly get started with TiDB Cloud Data Service (PREVIEW) by creating a Data App, developing, testing, deploying, and calling an endpoint. A Data App is a collection of endpoints that you can use to access data for a specific application.
The reason will be displayed to describe this comment to others. Learn more.
Major · Functional Correctness · Quick win
Resolve the merge conflict and remove the retired API link.
The file still contains <<<<<<< HEAD, =======, and >>>>>>> markers. The conflict also keeps /tidb-cloud/use-chat2query-api.md, which causes the reported internal-link failure and the MD003/MD022 diagnostics. Keep the PREVIEW introduction and remove the obsolete tip.
Apply this exact replacement
--- "a/tidb-cloud/data-service-get-started.md"+++ "b/tidb-cloud/data-service-get-started.md"@@ -7,17 +7,7 @@
Data Service (beta) enables you to access TiDB Cloud data via an HTTPS request using a custom API endpoint and allows you to seamlessly integrate with any application or service that is compatible with HTTPS.
-<<<<<<< HEAD-> **Tip:**->-> TiDB Cloud provides a Chat2Query API for {{{ .starter }}} instances. After it is enabled, TiDB Cloud will automatically create a system Data App called **Chat2Query** and a Chat2Data endpoint in Data Service. You can call this endpoint to let AI generate and execute SQL statements by providing instructions.->-> For more information, see [Get started with Chat2Query API](/tidb-cloud/use-chat2query-api.md).--This document introduces how to quickly get started with TiDB Cloud Data Service (beta) by creating a Data App, developing, testing, deploying, and calling an endpoint. A Data App is a collection of endpoints that you can use to access data for a specific application.-=======
This document introduces how to quickly get started with TiDB Cloud Data Service (PREVIEW) by creating a Data App, developing, testing, deploying, and calling an endpoint. A Data App is a collection of endpoints that you can use to access data for a specific application.
->>>>>>> d96fa6c87c (tidb-cloud: remove Chat2Query documentation (#24549))
## Before you begin
Committable suggestion
IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
<<<<<<< HEAD
> **Tip:**
>
> TiDB Cloud provides a Chat2Query API for {{{ .starter }}} instances. After it is enabled, TiDB Cloud will automatically create a system Data App called **Chat2Query** and a Chat2Data endpoint in Data Service. You can call this endpoint to let AI generate and execute SQL statements by providing instructions.
>
> For more information, see [Get started with Chat2Query API](/tidb-cloud/use-chat2query-api.md).
This document introduces how to quickly get started with TiDB Cloud Data Service (beta) by creating a Data App, developing, testing, deploying, and calling an endpoint. A Data App is a collection of endpoints that you can use to access data for a specific application.
=======
This document introduces how to quickly get started with TiDB Cloud Data Service (PREVIEW) by creating a Data App, developing, testing, deploying, and calling an endpoint. A Data App is a collection of endpoints that you can use to access data for a specific application.
This document introduces how to quickly get started with TiDB Cloud Data Service (PREVIEW) by creating a Data App, developing, testing, deploying, and calling an endpoint. A Data App is a collection of endpoints that you can use to access data for a specific application.
You can use your own keys in Alibaba Cloud Key Management Service (KMS) to encrypt data at rest, giving you greater control over data security and compliance.
This feature is now available upon request. For more information, see [Dual-Layer Data Encryption](/tidb-cloud/premium/dual-layer-data-encryption-premium.md).
The reason will be displayed to describe this comment to others. Learn more.
Minor · Functional Correctness · Quick win
Repair the dual-layer encryption link.
The internal-link check reports /tidb-cloud/premium/dual-layer-data-encryption-premium.md as invalid, and the reviewed revision does not contain that file. Update the link to the current documentation path or add the missing page. ()
When a TiDB Cloud Essential instance with existing backups is deleted, its backup files are moved to the Recycle Bin. Backup files created by automatic backups are retained in the Recycle Bin for a specified period. To avoid data loss, restore the data to a new TiDB Cloud Essential instance before the retention period expires. Note that if a TiDB Cloud Essential instance **has no backup**, the deleted instance is not displayed in the Recycle Bin.
For more information, see [Backup and Restore](/tidb-cloud/backup-and-restore-serverless.md#restore-from-recycle-bin).
The reason will be displayed to describe this comment to others. Learn more.
Minor · Functional Correctness · Quick win
Remove the dead Recycle Bin fragment.
The target page has no #restore-from-recycle-bin heading. Add the referenced section, or link to the actual Recycle Bin documentation instead of leaving a dead fragment. (raw.githubusercontent.com)
Tools
GitHub Actions: ci / 3_internal-links-anchors.txt
[warning] 644-644: remark-lint (pingcap-docs-anchors): Dead anchor /tidb-cloud/backup-and-restore-serverless.md#restore-from-recycle-bin.
GitHub Actions: ci / internal-links-anchors
[warning] 644-644: verify-link-anchors.sh (remark-lint): Dead anchor /tidb-cloud/backup-and-restore-serverless.md#restore-from-recycle-bin.
The reason will be displayed to describe this comment to others. Learn more.
Major · Functional Correctness · Quick win
Resolve all merge conflicts before publishing this page.
The file still contains conflict markers in the SQL Editor section and after the query-result section. The retained Chat2Query branch contains the deleted #chat2query anchor. The later block retains obsolete AI-generated SQL instructions. Remove all conflict markers and obsolete Chat2Query content. Keep the direct SQL example.
This violates the repository requirement to preserve Markdown, list, and link conventions.
Source: Path instructions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
area/developThis PR relates to the area of TiDB App development.area/tidb-cloudThis PR relates to the area of TiDB Cloud.do-not-merge/holdIndicates that a PR should not merge because someone has issued a /hold command.lgtmsize/XXLDenotes a PR that changes 1000+ lines, ignoring generated files.type/cherry-pick-for-masterThis PR is cherry-picked to master from a source PR.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ti-chi-bot
added
area/develop
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
This is an automated cherry-pick of #24549
What is changed, added or deleted? (Required)
Remove documentation for Chat2Query, which has been removed from the TiDB Cloud console, and its API, which is being retired.
explore-data-with-sql-editor.md, update inbound links, and redirect all four removed page URLs using aliases.Validation: scoped Markdownlint and internal link checks (25 files), plus
git diff --check.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)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit