Is your feature request related to a problem? Please describe.
Currently pinecone is the only supported Vector database. Other alternatives like Milvus, qdrant, deeplake, etc would allow a user to self-host their database and become part of the docker-compose stack to self-host more of the bots functionality.
Describe the solution you'd like
Refactor the current pinecone implementation, abstract the functionality either with a local handler for each alternative solution
Describe alternatives you've considered
Add more variables to the .env so that any of them could be enabled.
Additional context
I'm not sure if there would be a benefit or if potential issues would arise if multiple vector DB's were used simultaneously (eg, having both pinecone and Milvus being enabled)
Thanks for surfacing this! This project is out of active feature development, but I am willing to support this effort if anyone is willing to pick it up!
Is your feature request related to a problem? Please describe. Currently pinecone is the only supported Vector database. Other alternatives like Milvus, qdrant, deeplake, etc would allow a user to self-host their database and become part of the docker-compose stack to self-host more of the bots functionality.
Describe the solution you'd like Refactor the current pinecone implementation, abstract the functionality either with a local handler for each alternative solution
Describe alternatives you've considered Add more variables to the .env so that any of them could be enabled.
Additional context I'm not sure if there would be a benefit or if potential issues would arise if multiple vector DB's were used simultaneously (eg, having both pinecone and Milvus being enabled)