@yoheinakajima @francip with PR #186 and #218 pinecone is now an extension. It is not clear to me if the this mechanism is generic or specific to pinecone only (neither PRs seem to address this point)
Furthermore, PR #141 and #111 both had the same goal to add a new vector database but had very distinct approach. Development in these PRs seem to have halted now (but they're still open).
Could you please share some pointers or documentation on what is now the best way to add support for a vector vector database to babyagi?
141 and #111 are still open because we keep them as examples of implementing numpy, vecto, and weaviate, which I will get to (or someone else can do it) soon and build as extensions using the steps above.
@yoheinakajima @francip with PR #186 and #218 pinecone is now an extension. It is not clear to me if the this mechanism is generic or specific to pinecone only (neither PRs seem to address this point)
Furthermore, PR #141 and #111 both had the same goal to add a new vector database but had very distinct approach. Development in these PRs seem to have halted now (but they're still open).
Could you please share some pointers or documentation on what is now the best way to add support for a vector vector database to babyagi?