Repository navigation
ai: add vector search troubleshooting workflow - #24554
abigpigishere wants to merge 2 commits into
Conversation
|
Welcome @abigpigishere! |
|
Hi @abigpigishere. Thanks for your PR. I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
[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 |
|
|
Walkthrough
Merge Risk:
|
There was a problem hiding this comment.
Actionable comments posted: 1

Review info
-
Run configuration-
- Source mode: Auto
- Repository: pingcap/docs
- Branch: release-8.5
- File: .coderabbit.yaml
- Commit: 032ff0c
- Layers: Repository YAML
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
3ea30161-475a-4cc5-8ddf-0551b8601e1c
Files selected for processing: 3-
TOC-ai.mdai/guides/vector-search-troubleshooting.mdai/reference/vector-search-improve-performance.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
-
|
|
||
| Recent writes can reside in the Delta layer, and query performance can differ from that of fully indexed data. Unindexed data does not mean unsearchable data. For query behavior during index building, see [View index build progress](/ai/reference/vector-search-index.md#view-index-build-progress). | ||
|
|
||
| `TIFLASH_INDEXES` is experimental and its fields can change. Check `DESC INFORMATION_SCHEMA.TIFLASH_INDEXES;` for your version before using the query. See [`TIFLASH_INDEXES`](/information-schema/information-schema-tiflash-indexes.md). |
There was a problem hiding this comment.
Preserve the upstream production-use warning for TIFLASH_INDEXES.
The reference marks this table as experimental and says it is not recommended for production use. This guide directs users to query the table during slow-query investigations but only mentions field changes. Keep the stronger warning so readers do not treat the result as a stable production interface. (raw.githubusercontent.com)
> **Warning:** `TIFLASH_INDEXES` is experimental and is not recommended for use in production environments. Its fields can change between TiDB versions. Check `DESC INFORMATION_SCHEMA.TIFLASH_INDEXES;` for your version before using this query. See [`TIFLASH_INDEXES`](/information-schema/information-schema-tiflash-indexes.md).
First-time contributors' checklist
What is changed, added or deleted? (Required)
Add a troubleshooting workflow for vector searches that remain slow after a vector index has been created. The guide connects existing reference material into three checks: execution-plan index usage, unindexed Stable/Delta data, and first-versus-subsequent execution overhead. It includes diagnostic SQL, interpretation tables, and a compact checklist for reporting unresolved problems.
Add navigation in TOC-ai.md and a link from the existing performance guide. Query comparisons explicitly retain the original SQL, and the guide does not introduce benchmark claims or product behavior changes.
This PR targets release-8.5 because the repository's AI documentation workflow maintains the English source there and synchronizes Chinese AI documentation automatically.
Validation:
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