Update vector search cookbook md with new terminology

[SanjanaBoggaramJ]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @SanjanaBoggaramJ, 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 focuses on updating the terminology used in the vector search cookbook's README.md file. The changes ensure that the documentation accurately reflects the current naming conventions for Couchbase's vector search features, such as 'Search Vector Index' and 'Hyperscale Vector Index', providing a more consistent and up-to-date guide for users.

Highlights

• Terminology Update: Replaced 'FTS (Full Text Search)' with 'Search Vector Index' and 'GSI (Global Secondary Index)' with 'Hyperscale Vector Index, Composite Vector Index' throughout the README.md.
• Directory Path Change: Updated the example directory path from fts/ to search_based/ to reflect the new terminology.
• Documentation Clarity: Adjusted section titles and instructional text to align with the updated vector search index terminology, improving the clarity and accuracy of the cookbook's documentation.
• File Formatting: Ensured the README.md file ends with a newline character for better file hygiene.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• README.md
  • Updated 'FTS (Full Text Search)' to 'Search Vector Index'.
  • Updated 'GSI (Global Secondary Index)' to 'Hyperscale Vector Index, Composite Vector Index'.
  • Changed directory reference from fts/ to search_based/.
  • Renamed section title 'Couchbase Vector Search Index (FTS Approach Only)' to 'Couchbase Search Vector Index'.
  • Ensured the file ends with a newline.

Activity

• No specific activity (comments, reviews, etc.) has been recorded for this pull request yet.

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

[gemini-code-assist]

Code Review

This pull request updates the terminology in the README.md to reflect the latest naming conventions for Couchbase vector search features. The changes improve clarity and align the documentation with the product. However, I've identified a couple of areas for improvement. There's an inconsistency between the updated directory paths in the documentation and the actual directory structure in the repository, which could confuse users. Additionally, a minor grammatical correction is needed to improve readability. My review includes specific suggestions to address these points.

[VirajAgarwal1]

Thanks for the PR. I have just a couple of concerns before we merge.

[SanjanaBoggaramJ]

Hey Viraj, I addressed your comments. Please re-review

[VirajAgarwal1]

lgtm