Solr QueryQuery pipeline stage configuration specifications
The Solr Query stage transforms the Managed Fusion query pipeline
Request
object into a Solr query and sends it to Solr.
|
When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.
|
Sends the search request to Solr
skip - boolean
Set to true to skip this stage.
Default: false
label - string
A unique label for this stage.
<= 255 characters
condition - string
Define a conditional script that must result in true or false. This can be used to determine if the stage should process or not.
allowedRequestHandlers - array[string]
httpMethod - string
HTTP method for querying Solr.
Default: POST
Allowed values: POSTGET
allowFederatedSearch - boolean
Allow Solr 'collection' and 'shards' parameters.
Default: false
responseSignalsEnabled - boolean
If checked, this stage generates a 'response' signal containing metadata about the response from Solr. Response signals are used by App Insights and experiments. This setting only applies if the searchLogs and signals features are enabled for the collection. You may want to disable this option for auto-complete pipelines to avoid generating response signals as users type.
Default: true
excludeResponseSignalMatchRules - array[object]
If the 'Generate Response Signal' option is checked, then you can prevent generating a response signal based on specific parameters in the query, such as to enable response signals in general but to disable for auto-complete queries.
object attributes:{param
required : {
display name: Query Param
type: string
}pattern
required : {
display name: Regex Pattern
type: string
}}
preferredReplicaType - string
Nominate a replicate type that will be given a higher order of precedence when querying Solr. This preference will only be applied for queries that target multiple shards.
Allowed values: nonepulltlognrt