-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Replace Pinecone with Chroma DB as Default Vector Database #178
base: main
Are you sure you want to change the base?
Conversation
_header: 'GET /api/v1/collections/pdf-test/count HTTP/1.1\r\n' + throw new Error('Failed to ingest your data'); |
Hi @myaicreator! To connect to Chroma's backend - you either need to connect to a hosted version of Chroma, or run it on your local computer. If you can run docker-compose up -d --build you can run Chroma. git clone https://github.com/chroma-core/chroma.git
cd chroma
docker-compose up -d --build Described in depth, here: https://docs.trychroma.com/getting-started |
@redcpp Thanks for the PR. Chroma is a good choice, however the setup isn't easy for beginner users to set up atm. Once they move to a hosted a solution, the transition will be much easier. |
Looks like you may have missed a file... makechain.ts |
theres a way to connect to this example with chroma db ? |
I think, it is good choice to use Chroma DB. |
Is there any update on this yet? |
This is great, will try it soon. |
Description:
This pull allows users to use either the existing Pinecone option or the Chroma DB option. The change sets Chroma DB as the default selection. The proposed changes improve the application's costs and complexity while setting everything up.
Changes:
Updated the chat handler to allow choosing the preferred database.
Modified the code to use Chroma DB as the default selection for database operations.
Added an ingest option for Chroma DB.
Testing:
Manually tested the application to ensure that Chroma DB works correctly and is set as the default option.
Feel free to reach out if you have any questions or require further clarification on any aspect of this pull request.