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
We want to ensure that all vector stores throw similar errors. Currently, different vector stores throw their own specific errors when certain methods fail. For example, the chroma vector store can throw a specific error when the remove() method is called and fails, while the qdrant vector store throws a different error for the same situation.
The task would involve mapping the errors thrown by different vector stores to a set of generic errors.
Motivation
Standardizing error handling across vector stores will simplify error management, by allowing developers to use try/except blocks on any vector store without changing the exception type depending on the implementation. Developers will be able to handle errors in a consistent manner, regardless of the vector store implementation.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Feature description
We want to ensure that all vector stores throw similar errors. Currently, different vector stores throw their own specific errors when certain methods fail. For example, the chroma vector store can throw a specific error when the remove() method is called and fails, while the qdrant vector store throws a different error for the same situation.
The task would involve mapping the errors thrown by different vector stores to a set of generic errors.
Motivation
Standardizing error handling across vector stores will simplify error management, by allowing developers to use try/except blocks on any vector store without changing the exception type depending on the implementation. Developers will be able to handle errors in a consistent manner, regardless of the vector store implementation.
Additional context
No response
The text was updated successfully, but these errors were encountered: