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
I searched existing ideas and did not find a similar one
I added a very descriptive title
I've clearly described the feature request and motivation for it
Feature request
Extend the search methods of the AzureSearch vector store so that they accept some of the currently unexposed Azure AI Search search parameters, such as:
scoringProfile: Choose a non-default scoring profile for sorting
searchFields: Specify which fields are included in keyword search (for hybrid_search)
searchMode: Choose whether all or just one query term must match (for hybrid_search)
select: Specify a subset of fields to return for each document
Motivation
The current limitations make AzureSearch and AzureSearchVectorStoreRetriever unusable when more control is needed than currently provided. It should not be required to write a custom vector store / retriever implementation just to be able to pass an additional search parameter.
Proposal (If applicable)
Support at least the following keyword arguments for all AzureSearch search methods:
scoring_profile: str
select: list[str]
And the following for methods that perform hybrid searches:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Checked
Feature request
Extend the search methods of the
AzureSearch
vector store so that they accept some of the currently unexposed Azure AI Search search parameters, such as:scoringProfile
: Choose a non-default scoring profile for sortingsearchFields
: Specify which fields are included in keyword search (forhybrid_search
)searchMode
: Choose whether all or just one query term must match (forhybrid_search
)select
: Specify a subset of fields to return for each documentMotivation
The current limitations make
AzureSearch
andAzureSearchVectorStoreRetriever
unusable when more control is needed than currently provided. It should not be required to write a custom vector store / retriever implementation just to be able to pass an additional search parameter.Proposal (If applicable)
Support at least the following keyword arguments for all
AzureSearch
search methods:scoring_profile: str
select: list[str]
And the following for methods that perform hybrid searches:
search_fields: list[str]
search_mode: str
Beta Was this translation helpful? Give feedback.
All reactions