Apache Solr Reference Guide Covering Apache Solr 6.0

faceting 5 true 7 true 7
add multiple
values,
maintaining
order
true
field length
affects doc
score
false
MoreLikeThis
5
true 6
Notes:
1 Recommended but not necessary.
2 Will be used if present, but not necessary.
3 (if termVectors=true)
4 A tokenizer must be defined for the field, but it doesn't need to be indexed.
5 Described in Understanding Analyzers, Tokenizers, and Filters.
6 Term vectors are not mandatory here. If not true, then a stored field is analyzed. So term vectors are
recommended, but only required if stored=false.
7 Either indexed or docValues must be true, but both are not required. DocValues can be more efficient in
many cases.
Defining Fields
Fields are defined in the fields element of schema.xml. Once you have the field types set up, defining the fields
themselves is simple.
Example
The following example defines a field named price with a type named float and a default value of 0.0; the i
ndexed and stored properties are explicitly set to true, while any other properties specified on the float fiel
d type are inherited.
Field Properties
Property
name
Description
The name of the field. Field names should consist of alphanumeric or underscore characters only
and not start with a digit. This is not currently strictly enforced, but other field names will not have
first class support from all components and back compatibility is not guaranteed. Names with both
leading and trailing underscores (e.g. _ version_ ) are reserved. Every field must have a name.
type The name of the fieldType for this field. This will be found in the " name" attribute on the field
Type definition. Every field must have a type.
Apache Solr Reference Guide 6.0
67