[WIP] tidbcloud: Add auto embedding docs

[breezewish]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

Note: This is still a work in progress.

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lilin90 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.

Needs approval from an approver in each of these files:

• OWNERS

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

[gemini-code-assist]

Summary of Changes

Hello @breezewish, I'm Gemini Code Assist¹! 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 introduces new documentation for TiDB Cloud's 'Auto Embedding' feature, designed to simplify vector search by automatically converting text into vector embeddings. The changes include an overview of the feature and specific guides for integrating various embedding models, making it easier for users to leverage semantic search capabilities.

Highlights

• New Documentation for Auto Embedding: I've added comprehensive documentation for the new 'Auto Embedding' feature in TiDB Cloud, which allows users to perform vector search directly on text data without manual vector generation.
• Overview of Auto Embedding: A new overview page (tidb-cloud/vector-search-auto-embedding-overview.md) has been introduced, explaining the core concepts, workflow, and benefits of Auto Embedding, including quick start examples and its compatibility with vector indexes.
• Specific Embedding Model Guides: Detailed documentation pages have been added for various embedding models supported by TiDB Cloud, including Amazon Titan, Cohere, and Gemini. These guides provide information on available models, SQL usage examples, and configuration options for both TiDB Cloud-hosted and Bring Your Own Key (BYOK) models.
• Table of Contents Update: The TOC-tidb-cloud.md file has been updated to include a new 'Auto Embedding' section under 'Vector Search', linking to the newly added overview and individual model documentation pages.

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 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 or fill out our survey 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

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

[gemini-code-assist]

Code Review

This pull request adds new documentation for the "Auto Embedding" feature. The changes include updating the Table of Contents and adding several new documentation pages for the feature overview and specific embedding models (Amazon Titan, Cohere, Gemini).

The new documentation is well-structured and detailed. I've found a few minor issues related to grammar, typos, and wording that could improve clarity and consistency. These are mostly low-severity suggestions.

I've referenced the following points from the style guide in my review:

• Clarity and Simplicity (line 14): Suggested more direct and professional wording.
• Correct English grammar, spelling, and punctuation (line 20): Pointed out typos and grammatical mistakes.
• Consistent terminology (line 25): Recommended consistent capitalization for "documentation".

[gemini-code-assist]

There's a grammatical error here.¹ It should be "You must use" instead of "You must using".

Style Guide References

Suggested change

	> You must using `VEC_COSINE_DISTANCE` or `VEC_L2_DISTANCE` when defining the vector index, while using `VEC_EMBED_COSINE_DISTANCE` or `VEC_EMBED_L2_DISTANCE` when performing vector search queries.
	> You must use `VEC_COSINE_DISTANCE` or `VEC_L2_DISTANCE` when defining the vector index, while using `VEC_EMBED_COSINE_DISTANCE` or `VEC_EMBED_L2_DISTANCE` when performing vector search queries.

Footnotes

1. The style guide requires correct English grammar, spelling, and punctuation. (link) ↩

[gemini-code-assist]

The phrase "it will just work" is a bit informal for technical documentation. I suggest a more professional alternative to maintain clarity and a consistent tone.¹

Style Guide References

Suggested change

	Auto embedding is compatible with [Vector Index](/vector-search/vector-search-index.md) for better query performance. Define a vector index over the generated vector column, and it will just work:
	Auto embedding is compatible with [Vector Index](/vector-search/vector-search-index.md) for better query performance. Define a vector index over the generated vector column, and it is used automatically:

Footnotes

1. The style guide prioritizes clarity and simplicity in documentation. (link) ↩

[ti-chi-bot]

@breezewish: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-verify	ca6a494	link	true	/test pull-verify

Full PR test history. Your PR dashboard.

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.