Skip to content
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

[Enhancement]: Ability to use the vector-store as a cache #638

Open
shashankram opened this issue Aug 8, 2024 · 3 comments
Open

[Enhancement]: Ability to use the vector-store as a cache #638

shashankram opened this issue Aug 8, 2024 · 3 comments

Comments

@shashankram
Copy link

What would you like to be added?

Provide the ability to use the vector store in use for caching as well. For e.g., if I am using Weaviate, I would like to use it for both caching and vector storage.

Thanks

Why is this needed?

No response

Anything else?

No response

@SimFG
Copy link
Collaborator

SimFG commented Aug 8, 2024

I think this is not a very good idea, because in this caching process, the scalar data will generally be very large, that is, the data size of the questions and their answers is large, and it is not suitable to store them in the vector database, because the advantage of the vector database is vector storage and its search. If many scalars are placed in the vector database, on the one hand, it will not be conducive to retrieval, and on the other hand, it will greatly increase the pressure on the vector database and cause a waste of resources.

@shashankram
Copy link
Author

I understand, though the operational complexity with using multiple datastores for caching and vectorization is high. For smaller deployments, I was wondering if using the vector store as a cache for the scalar data would be feasible.

@SimFG
Copy link
Collaborator

SimFG commented Aug 9, 2024

For this case, you can try using sqlite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants