-
Notifications
You must be signed in to change notification settings - Fork 701
release-8.5: update the note about vector search support #21365
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
base: release-8.5
Are you sure you want to change the base?
release-8.5: update the note about vector search support #21365
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 provides a comprehensive update to the TiDB documentation, aligning it with the 8.5 release. It introduces new content for recently added features, clarifies existing functionalities, and improves the overall structure and navigability of the documentation for both TiDB Cloud and TiDB Self-Managed users.
Highlights
- Documentation Structure and Content: The Table of Contents for both TiDB Cloud and TiDB Self-Managed documentation has been significantly restructured and expanded. This includes new top-level sections like 'Key Concepts', 'CLI Reference', and 'Support Plan' for TiDB Cloud, and a new 'SQL Reference' section for TiDB Self-Managed. Many existing sections have been reorganized and updated.
- New Feature Documentation: New documentation has been added for C# connectivity, multi-column index optimization, the Index Advisor feature, and various batch processing capabilities (Pipelined DML, non-transactional DML,
IMPORT INTO
). - Vector Search Enhancements: Notes and links related to vector search support have been updated and expanded, including new integrations like Amazon Bedrock and details on full-text and hybrid search.
- Database Behavior Clarifications: The documentation for
AUTO_INCREMENT
andAUTO_RANDOM
has been updated to clarify their behavior, including details on MySQL compatibility mode, ID caching, and cache clearing procedures. Information on TiKV MVCC In-Memory Engine (IME) has also been added. - Administrative and Operational Updates: The
OWNERS
file has been updated to reflect changes in approver roles. Numerous minor fixes, link updates (including version-specific links), and clarifications have been applied across various documentation files, along with updates tolycheeignore
for link checking.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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 is currently in preview and 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 to provide feedback.
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
-
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. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request updates the note about vector search support in several markdown files, specifying that the feature is available for TiDB Self-Managed (TiDB >= v8.4) and TiDB Cloud Serverless, but not for TiDB Cloud Dedicated. The changes also convert the link to TiDB Cloud Serverless to a markdown link.
df44cd2
to
4b4dfa7
Compare
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
4b4dfa7
to
2e12a3c
Compare
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?