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

feat: Update VectorStore Base class and Introduce more Integrations #649

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

ishaansehgal99
Copy link
Collaborator

@ishaansehgal99 ishaansehgal99 commented Oct 23, 2024

Reason for Change:
Cleans up vector store classes by putting common logic in the base class and inheriting from their.

With new base class also introduces two new popular integrations - azurecosmosdb mongodb, chromadb

index.set_index_id(index_name)
self.index_map[index_name] = index
self.index_store.add_index_struct(index.index_struct)
self._persist(index_name)
Copy link
Member

@zhuangqh zhuangqh Oct 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am thinking about a question: will the persist fails here? or we should rollback something

Copy link
Collaborator Author

@ishaansehgal99 ishaansehgal99 Oct 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its possible, added a try-catch in persist function to help catch this

Copy link
Member

@zhuangqh zhuangqh Oct 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if persist fails, should we rollback the index_store? Or there will be some inconsistencies between index_store and storage

ragengine/vector_store/base.py Outdated Show resolved Hide resolved
@ishaansehgal99 ishaansehgal99 changed the title feat: Update VectorStore Base class and Introduce ChromaDB feat: Update VectorStore Base class and Introduce more Integrations Oct 24, 2024
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

Successfully merging this pull request may close these issues.

2 participants