Update langchain4j

[Arjunnr-cb]

changed fts to search vector index

[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 updates the langchain4j tutorial documentation to align with current terminology for vector indexing. The change specifically replaces references to "FTS vector index" with "search vector index" throughout the document, ensuring the tutorial accurately reflects the underlying technology and its nomenclature. This improves clarity and consistency for users learning about Couchbase's embedding store integration.

Highlights

• Terminology Update: Replaced all instances of "FTS vector index" with "search vector index" to reflect updated terminology in the Couchbase langchain4j integration tutorial.

🧠 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/java/langchain4j.md
  • Updated terminology from "FTS vector index" to "search vector index" in the "Couchbase Embedding Store" section.
  • Corrected the description of initialization parameters to refer to "search vector index" instead of "FTS vector index".
  • Revised the "Vector Index" section to consistently use "search vector index" for vector similarity lookups.

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 from 'FTS vector index' to 'search vector index' in the LangChain4j tutorial. The changes introduce a minor grammatical error by using 'an' instead of 'a' before 'search vector index', which I've provided suggestions to fix. For consistency, you may also want to update similar terminology in other documentation files if it's within the scope of this change.

[VirajAgarwal1]

lgtm