Skip to content

Conversation

@shyam-cb
Copy link
Contributor

No description provided.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @shyam-cb, 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 refines the descriptions for two tutorials, one integrating Haystack and another LlamaIndex, with OpenAI for Retrieval-Augmented Generation (RAG). The primary purpose of these changes is to standardize and accurately reflect the use of Couchbase's GSI (Global Secondary Index) vector indexing capabilities, ensuring consistency in terminology across the documentation.

Highlights

  • Documentation Update: Corrected terminology in the description of the Haystack RAG tutorial, replacing 'Hyperscale vector index' with 'GSI vector index' and 'Hyper scale vector search' with 'GSI vector search'.
  • Documentation Update: Corrected terminology in the description of the LlamaIndex RAG tutorial, updating references from 'Hyperscale vector search' to 'GSI vector search' and 'vector search capabilities' to 'GSI vector search capabilities'.
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.

@shyam-cb shyam-cb merged commit 020da67 into couchbase-examples:main Oct 30, 2025
0 of 2 checks passed
Copy link
Contributor

@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 descriptions for the Haystack and LlamaIndex GSI examples to better align with the tutorial content. The changes replace references from 'Hyperscale' to the more general 'GSI' (Global Secondary Index), which accurately reflects the technology showcased. The updates are an improvement, and I have one minor suggestion to enhance terminological consistency between the two modified files.

description:
- Learn how to build a semantic search engine using Couchbase's Hyperscale vector index.
- This tutorial demonstrates how to integrate Couchbase's Hyper scale vector search capabilities with OpenAI embeddings.
- Learn how to build a semantic search engine using Couchbase's GSI vector index.
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For consistency with the corresponding LlamaIndex example (lamaindex/gsi/___frontmatter._____md) and with line 8 in this file, consider using "GSI vector search" instead of "GSI vector index". While both terms are technically correct, using "GSI vector search" consistently across the examples would improve clarity for the reader.

Suggested change
- Learn how to build a semantic search engine using Couchbase's GSI vector index.
- Learn how to build a semantic search engine using Couchbase's GSI vector search.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant