You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on a project that needs Embeddings and Vector stores.
Langchain has support for tons of Embedding stores. Noticed there's also support for Redis. Since, Redis was already in my stack decided to go with this.
Later on I discovered that even though Redis as vector store is technically supported, the support is very basic.
For example delete is not implemented. Also because of the way indexes are generated, data gets overwritten each time I add documents to already existing index, I think. I had to find out all of this by digging in the source code. I think this is not documented anywhere.
I'm currently working on adding these features, but in the meantime had to settle for something else.
I believe that if we had separate repo for Redis vectorstore implementation, it would be easier to manage the documentation and Pull Requests.
I think, library contains tons and tons of features and it will only keep growing larger. I think sooner or later we'll hit a point where it's hard to maintain everything in a single repo.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm currently working on a project that needs Embeddings and Vector stores.
Langchain has support for tons of Embedding stores. Noticed there's also support for Redis. Since, Redis was already in my stack decided to go with this.
Later on I discovered that even though Redis as vector store is technically supported, the support is very basic.
For example delete is not implemented. Also because of the way indexes are generated, data gets overwritten each time I add documents to already existing index, I think. I had to find out all of this by digging in the source code. I think this is not documented anywhere.
I'm currently working on adding these features, but in the meantime had to settle for something else.
I believe that if we had separate repo for Redis vectorstore implementation, it would be easier to manage the documentation and Pull Requests.
I think, library contains tons and tons of features and it will only keep growing larger. I think sooner or later we'll hit a point where it's hard to maintain everything in a single repo.
Beta Was this translation helpful? Give feedback.
All reactions