Skip to content

.Net: [MEVD] VectorStoreOperationException should more narrowly wrap only the database call #11766

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.

Sign up for GitHub

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

Jump to bottom
Open
roji opened this issue Apr 28, 2025 · 0 comments
Open

.Net: [MEVD] VectorStoreOperationException should more narrowly wrap only the database call #11766

roji opened this issue Apr 28, 2025 · 0 comments
Labels
msft.ext.vectordata Related to Microsoft.Extensions.VectorData .NET Issue or Pull requests regarding .NET code

Comments

@roji
Copy link
Member

roji commented Apr 28, 2025

In some connectors, exceptions coming out of filter translation are wrapped by VectorStoreOperationException, while in others they are not. Such exceptions (e.g. an untranslatable filter) represent application bugs and shouldn't be wrapped by VectorStoreOperationException (they're never meant to be caught and handled).

/cc @westey-m @dmytrostruk
@roji roji added .NET Issue or Pull requests regarding .NET code msft.ext.vectordata Related to Microsoft.Extensions.VectorData labels Apr 28, 2025
@roji roji moved this to Backlog: Not Planned in Semantic Kernel Apr 28, 2025
@github-actions github-actions bot changed the title [MEVD] VectorStoreOperationException should more narrowly wrap only the database call .Net: [MEVD] VectorStoreOperationException should more narrowly wrap only the database call Apr 28, 2025
@roji roji moved this from Backlog: Not Planned to Backlog in Semantic Kernel Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
msft.ext.vectordata Related to Microsoft.Extensions.VectorData .NET Issue or Pull requests regarding .NET code
Projects
Semantic Kernel
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roji @markwallace-microsoft