Da-1335 update bedrock serverless pdf chat

[Arjunnr-cb]

changes made according to the 8.0 terminologies

[gemini-code-assist]

Summary of Changes

Hello @Arjunnr-cb, 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 bedrock-serverless-pdf-chat tutorial to incorporate the latest terminology from Couchbase 8.0. The changes ensure that the documentation accurately reflects current product naming, specifically by replacing references to 'FTS' with 'Vector Search' or 'Search Vector Index' for improved clarity and consistency.

Highlights

• Terminology Update: Updated the technology metadata in the tutorial's front matter from fts to vector search to align with Couchbase 8.0 terminology.
• Environment Variable Renaming: Modified the example INDEX_NAME environment variable description to use name_of_search_vector_index_with_vector_support instead of name_of_fts_index_with_vector_support, reflecting the updated naming conventions.

🧠 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

• tutorial/markdown/python/bedrock-serverless-pdf-chat/bedrock-serverless-pdf-chat.md
  • Changed the technology field in the YAML front matter from fts to vector search.
  • Updated the placeholder value for INDEX_NAME in the environment variable section from name_of_fts_index_with_vector_support to name_of_search_vector_index_with_vector_support.

Activity

• No specific activity (comments, reviews, or progress updates) 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 Bedrock serverless PDF chat tutorial to align with Couchbase 8.0 standards, which is a great improvement. The changes from 'fts' to 'vector search' and updating the index name placeholder are correct. To further improve consistency, you might consider replacing the remaining instances of 'Full Text Service' with 'Search Service' in this document (e.g., on lines 86 and 88), as this is also part of the new terminology.

[VirajAgarwal1]

Some minor changes are needed, and we're good to merge the PR.

[VirajAgarwal1]

The tutorial section titled “Create the Search Index on Full Text Service” and its surrounding prose still uses “Full Text Service”. Per the guide’s terminology consistency section (and Gemini’s comment), this should be updated to Search Service.

[VirajAgarwal1]

Search Vector Index (the FTS/Search-service-based vector index type) is preferred over generic “vector index”/FTS terminology. This tutorial currently mixes “Search Index”, “vector index”, and “Vector Search”.