-
Notifications
You must be signed in to change notification settings - Fork 683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
note for TiDB Vector Search #19373
Comments
@shawn0915 Thank you for bringing this up. Let me clarify: The document at https://docs.pingcap.com/tidbcloud/vector-search-get-started-using-python is specifically for TiDB Cloud users. The "beta" status and "only available for TiDB Cloud Serverless clusters" statement refers to the feature's availability within TiDB Cloud - meaning it's not yet supported on TiDB Cloud Dedicated clusters. If you're interested in Vector Search documentation for TiDB v8.4, please refer to the TiDB Self-Managed documenattion at https://docs.pingcap.com/tidb/v8.4/vector-search-get-started-using-python. |
@Oreoxmt thanks for reply.
It is better to clarify the scope or the description like "available for TiDB Self-Managed clusters and [TiDB Cloud Serverless]" in both sides?
https://docs.pingcap.com/tidb/v8.4/vector-search-get-started-using-python
https://docs.pingcap.com/tidbcloud/vector-search-get-started-using-python
BTW, in tidb docs, "vector search" should be "Vector Search"? |
|
Maybe we need to change occurance to this everywhere, like: TiDB Vector Search is currently in beta and is not available for TiDB Cloud Dedicated clusters. This could lead to less confusions. |
Yes, I've created a PR #19385 to standardize the capitalization of “vector search” and “Vector Search” across the TiDB Cloud documentation to improve consistency and readability. The changes follow these rules:
|
I guess a recent misunderstanding caused by current Serverless doc is here: pingcap/autoflow#399 |
File: /release-7.5/tidb-cloud/vector-search-get-started-using-python.md
we need to update this content cause tidb 8.4 release?
The text was updated successfully, but these errors were encountered: