Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.Net: Fix Chroma notebook to actually use ChromaMemoryStore #9083

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

sujitdmello
Copy link

Motivation and Context

This PR applies to the dotnet implementation.

The 09-memory-with-chroma notebook uses the VolatileMemoryStore which appears to be a copy and paste from 06-memory-and-embeddings notebook. However, since the notebook wants to show the usage of Chroma, a small change has been made to use the actual ChromaMemoryStore instead.

Description

The notebook has been updated to include the Chroma connector package and use the ChromaMemoryStore class using the default URL http://localhost:8080 which is expected to be running in a Docker container as per the instructions in the notebook.

The notebook was tested with a Chroma instance, and it worked as expected.

Contribution Checklist

@sujitdmello sujitdmello requested a review from a team as a code owner October 3, 2024 16:59
@markwallace-microsoft markwallace-microsoft added the .NET Issue or Pull requests regarding .NET code label Oct 3, 2024
@github-actions github-actions bot changed the title Use the ChromaMemoryStore class to show the use of Chroma in the notebook .Net: Use the ChromaMemoryStore class to show the use of Chroma in the notebook Oct 3, 2024
@sujitdmello sujitdmello changed the title .Net: Use the ChromaMemoryStore class to show the use of Chroma in the notebook .Net: Fix Chroma notebook to actually use ChromaMemoryStore Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.NET Issue or Pull requests regarding .NET code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants