-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Feature Request] Add support for OpenSearch as a Vector Database #1955
Comments
Thank you @sushantgundla7, agree we should support opensearch! would you be open to working with us to add it as a vector store? |
Since you're a heavy user, it would be great to get your expertise as well |
Hey @sushantgundla7, |
@ashpreetbedi @Dev79844 Sure! :) |
I will push the basic code for the opensearch wrapper and leave few function signatures which you can implement. Also refer to the implementation of other vectordbs in the codebase, you will get an idea on how vectordbs are integrated. |
@Dev79844 |
Problem Description
I often find it frustrating when I cannot use OpenSearch as a vector database in Agno because it limits my ability to leverage OpenSearch's robust search and analytics capabilities for handling vector data.
Proposed Solution
Integrate OpenSearch as a vector database option within Agno. This feature should allow users to store and query vector data using OpenSearch seamlessly. Ensure compatibility with existing features such as memory management, knowledge stores, and multi-agent support. Provide comprehensive documentation and examples to help users get started with OpenSearch.
I have considered using other vector databases supported by Agno, but they do not offer the same level of performance and scalability as OpenSearch. Additionally, using a different vector database would require significant changes to my existing infrastructure, which is already optimized for OpenSearch.
I’m open to collaborating but need guidance on what functions are needed and how they will be integrated with agents.
The text was updated successfully, but these errors were encountered: