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

Allow users to define their own Vector DB as their cache #28

Open
ishaan-jaff opened this issue Jul 12, 2023 · 2 comments
Open

Allow users to define their own Vector DB as their cache #28

ishaan-jaff opened this issue Jul 12, 2023 · 2 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed high priority

Comments

@ishaan-jaff
Copy link
Contributor

Allow users to define their own Vector DB for the Cache. For compliance reasons users want the ability to define their own vector DB as cache

cc @grski

@grski
Copy link
Collaborator

grski commented Jul 12, 2023

@hkorzeniewski for tomorrow fyi

@grski
Copy link
Collaborator

grski commented Jul 15, 2023

For now we do not need vectorDB as we r doing simply an exact match with the cache - this is implemented here:#33
In the future next steps will include proper vector store/db and semantic similarity matches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed high priority
Projects
None yet
Development

No branches or pull requests

2 participants