Skip to content

Conversation

@ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #21967

First-time contributors' checklist

What is changed, added or deleted? (Required)

Add notes to clarify the availability of FULLTEXT syntax and indexes for different product options.

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.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot ti-chi-bot added area/tidb-cloud This PR relates to the area of TiDB Cloud. lgtm size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-master This PR is cherry-picked to master from a source PR. labels Oct 28, 2025
@gemini-code-assist
Copy link

Summary of Changes

Hello @ti-chi-bot, 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 enhances the clarity of documentation regarding FULLTEXT search capabilities within TiDB. It provides precise details on which TiDB deployment options (e.g., Cloud Starter/Essential vs. Self-Managed/Dedicated) fully support FULLTEXT indexes, ensuring users have accurate expectations about this feature's availability and limitations.

Highlights

  • Clarified FULLTEXT Index Support: Detailed information has been added regarding the availability and limitations of FULLTEXT syntax and indexes across different TiDB product options, ensuring users understand where this feature is fully supported.
  • Specific Product Availability: The documentation now explicitly states that FULLTEXT indexes are only fully supported in {{{ .starter }}} and {{{ .essential }}} clusters within specific AWS regions.
  • Parsing vs. Usage Distinction: The updated content clearly differentiates between parsing FULLTEXT syntax (which is supported by TiDB Self-Managed and TiDB Cloud Dedicated) and actually using FULLTEXT indexes (which is not supported by these versions).
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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

  1. 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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation to clarify the support for FULLTEXT syntax and indexes across different TiDB product offerings. The changes are accurate and helpful. I've provided a few minor suggestions to improve grammar and conciseness, in line with the repository's style guide.

@qiancai
Copy link
Collaborator

qiancai commented Oct 28, 2025

/approve

@ti-chi-bot
Copy link

ti-chi-bot bot commented Oct 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the approved label Oct 28, 2025
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@qiancai qiancai added the needs-cherry-pick-master Should cherry pick this PR to master branch. label Oct 28, 2025
@ti-chi-bot ti-chi-bot bot merged commit e1f5de2 into pingcap:master Oct 28, 2025
9 checks passed
@ti-chi-bot
Copy link
Member Author

In response to a cherrypick label: base branch (master) needs to differ from target branch (master).

@ti-chi-bot ti-chi-bot bot deleted the cherry-pick-21967-to-master branch October 28, 2025 01:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved area/tidb-cloud This PR relates to the area of TiDB Cloud. lgtm needs-cherry-pick-master Should cherry pick this PR to master branch. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-master This PR is cherry-picked to master from a source PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants