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.

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

.Net: Document supported filter clauses for each Vector Store connector #10138

Open
westey-m opened this issue Jan 9, 2025 · 0 comments
Open

.Net: Document supported filter clauses for each Vector Store connector #10138

westey-m opened this issue Jan 9, 2025 · 0 comments
Assignees
@westey-m
Labels
memory connector .NET Issue or Pull requests regarding .NET code sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) triage

Comments

@westey-m
Copy link
Contributor

westey-m commented Jan 9, 2025

Most DBs support all the filter clauses that we have, but there are some limited exceptions. We should document this on the page for each connector, so that it is clear to users what to expect.
@westey-m westey-m added .NET Issue or Pull requests regarding .NET code memory connector sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) labels Jan 9, 2025
@westey-m westey-m self-assigned this Jan 9, 2025
@github-actions github-actions bot changed the title .net: Document supported filter clauses for each Vector Store connector .Net: Document supported filter clauses for each Vector Store connector Jan 9, 2025
@westey-m westey-m moved this to Sprint: Planned in Semantic Kernel Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@westey-m westey-m

Labels
memory connector .NET Issue or Pull requests regarding .NET code sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) triage
Projects
Semantic Kernel
Status: Sprint: Planned
Milestone
No milestone
Development

No branches or pull requests
2 participants
@markwallace-microsoft @westey-m