Python: Fix: use k instead of k_nearest_neighbors in Azure Search vector …
#3333
+2
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
changed the title
k instead of k_nearest_neighbors in Azure Search vector …k instead of k_nearest_neighbors in Azure Search vector …
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes incorrect parameter naming in Azure AI Search vector query calls that was causing SDK warnings.
Changes:
- Replaced
k_nearest_neighborsparameter withkin VectorizableTextQuery and VectorizedQuery instantiations to align with the azure-search-documents SDK
corradopignato
force-pushed
the
fix/azure-search-vector-k-param
branch
from
6419e0b to
8e442f5
Compare
Member
|
@farzad528 can you doublecheck this? |
Member
Python Test Coverage Report •
Python Unit Test Overview
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
calls to VectorizedQuery / VectorizableTextQuery pass k_nearest_neighbors, which is not a recognized attribute of the azure-search-documents SDK. The correct attribute is k.
This causes warnings such as:
k_nearest_neighbors is not a known attribute of class and will be ignored
Description
In the function _semantic_search in _search_provider.py, replace every occurrence of k_nearest_neighbors with k (used by VectorizableTextQuery / VectorizedQuery) to match the azure-search-documents SDK.