-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Integrating OpenAI Embeddings with Pinecone Database #122
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Moving forward, I propose the following enhancements: Implement a feature to upload documents to the vector database through the existing UI. Add support for other vector databases recommended by OpenAI. |
@argen666 does this work right now? |
yes, just set up your Pinecone API key and try |
Going to try ! |
Thank you @argen666 for the PR! As a newbie, I have a few questions though:
Also, I receive this error after setting up my API key and using the feature: What am I doing wrong? Thank you again! |
|
is there a way this can be implemented with mogodb? |
@CyberRide yep, I have a plan to implement it in the next PR :) |
Wouldn't it be better to use something like LlamaIndex (https://github.com/jerryjliu/llama_index) which is open source & selfthosted rather than pinecone? It also has LangChain integration. |
Hi @psociety, I have a plan to implement all supported index storages in the next PR :) |
Hello,
I have added a feature to big-agi that integrates OpenAI embeddings with Pinecone, a vector database service. This feature leverages the power of semantic search by making it possible to store and retrieve OpenAI embeddings efficiently. This will improve the AI's ability to understand and generate responses based on the semantic meaning of the input.
Details:
Added Settings panel for Embeddings and Pinecone configuration
Integrated this service with the existing AI functionality of the app. Embeddings mode can be activated by double click on the Chat button
The new feature adheres to the current tech stack of the project, i.e., Next.js and React.
Please review my changes. I would appreciate any feedback.
Thank you!