[DOC]:Update google-gemini.md #5031
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
β Pull Request Title:
Fix incorrect embedding function name in Chroma-Gemini integration
π Description:
This PR corrects a typo in the embedding function used with the Chroma vector database and Google Gemini integration.
π§ Changes Made:
Replaced GoogleGenerativeAiEmbeddingFunction with the correct GoogleGeminiEmbeddingFunction from @chroma-core/google-gemini.
This resolves runtime errors such as:
TypeError: GoogleGenerativeAiEmbeddingFunction is not a constructor
β Why this is needed:
The incorrect function name causes apps to crash when initializing the embedding function.
This fix ensures proper instantiation of the embedding function and enables successful usage of Gemini embeddings with ChromaDB.-----This is done in js code
Description of changes
Summarize the changes made by this PR.
Test plan
How are these changes tested?
pytest
for python,yarn test
for js,cargo test
for rustDocumentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?