|
allowFederatedSearch
Allow Federated Search
|
Allow Solr 'collection' and 'shards' parameters.
type: boolean
default value: 'false'
|
|
allowedRequestHandlers
Configure Request Handlers Allowed for Queries
|
type: array of string
minimum number of items (minItems): 0
|
|
excludeResponseSignalMatchRules
Exclude Response Signal Criteria
|
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.
type: array of object
object attributes: {
param
(required)
: {
display name: Query Param
type: string
description : The name of the param to match
}
pattern
(required)
: {
display name: Regex Pattern
type: string
description : Pattern to match the param value against. The value may be a regex pattern.
format : regex
}
}
|
|
httpMethod
HTTP Method
|
HTTP method for querying Solr.
type: string
default value: 'POST'
enum: {
POST
GET
}
|
|
preferredReplicaType
Preferred Replica Type
|
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.
type: string
enum: {
none
pull
tlog
nrt
}
|
|
responseSignalsEnabled
Generate Response Signal
|
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.
type: boolean
default value: 'true'
|