Apache Solr Reference Guide Covering Apache Solr 6.0

have a single request handler that should return different fields, you can define the overriding parameters in
individual sections as usual.
The properties and configuration of an section mirror the properties and configuration of a
request handler. It can include sections for defaults, appends, and invariants, the same as any request handler.
For example, here is one of the sections defined by default in the data_driven_config exam
ple:
_text_
This sets the default search field ("df") to be "_text_" for all of the request handlers named in the path section. If
we later want to change the /query request handler to search a different field by default, we could override the
by defining the parameter in the section for /query.
The syntax and semantics are similar to that of a
property
. The following are the attributes
Description
path
name
A comma-separated list of paths which will use the parameters. Wildcards can be used in paths to
define nested paths, as described below.
The name of this set of parameters. The name can be directly in a requestHandler definition if a
path is not explicitly named. If you give your a name, you can refer to the params
in a that is not defined as a path.
For example, if an section has the name "myParams", you can call the name
when defining your request handler:
Wildcards
An section can support wildcards to define nested paths that should use the parameters
defined. A single asterisk (*) denotes that a nested path one level deeper should use the parameters. Double
asterisks (**) denote all nested paths no matter how deep should use the parameters.
For example, if we have an that looks like this:
_text_
10
title
Apache Solr Reference Guide 6.0
448