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

No support for vector search in azure ai foundry SDK #39713

Open
kuljotSB opened this issue Feb 13, 2025 · 1 comment
Open

No support for vector search in azure ai foundry SDK #39713

kuljotSB opened this issue Feb 13, 2025 · 1 comment
Labels
AI Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@kuljotSB
Copy link

kuljotSB commented Feb 13, 2025

I am working on the azure ai foundry SDK, the one that you use with azure ai agent service, for quite some time now and recently worked with the SDKs support for azure ai search. Although the SDK works pretty well, i believe it’s missing one vital feature - vector search.

I have created a vector index in azure ai search and would like to perform a vector search on it but unfortunately don’t see it being supported by the SDK. I have defined azure ai search connection as a tool during agent creation but don’t see a place to specify the embedding engine that I would want to use to generate vector embedding for the user query as part of the retrieval step. I believe all that it’s doing is just performing a keyword search and not a vector search.

An alternative to this method would be to create a user defined function encapsulated into a toolset during agent creation that implements my RAG architecture with the vector search capability into it but that would just make my code dirty and snatch away the abstraction that the SDK is aimed at providing developers with.

Am i missing something in the documentation or it’s just a feature that’s just not supported by the SDK as of now.

Any help would be highly appreciated!

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Feb 13, 2025
@xiangyan99 xiangyan99 added feature-request This issue requires a new behavior in the product in order be resolved. Service Attention Workflow: This issue is responsible by Azure service team. AI and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Feb 13, 2025
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Feb 13, 2025
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @achauhan-scc @kingernupur @luigiw @needuv @paulshealy1 @singankit.

@kristapratico kristapratico added the Client This issue points to a problem in the data-plane of the library. label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AI Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants