Docs: Reword note regarding _source for accuracy

Previously it suggested _source was always present, when that is not the case.

Closes #8491
This commit is contained in:
dw 2014-11-16 06:54:34 +00:00 committed by Clinton Gormley
parent feb465f26f
commit ad408eee85
1 changed files with 4 additions and 3 deletions

View File

@ -87,8 +87,10 @@ The following table lists all the attributes that can be used with the
Defaults to the property/field name.
|`store` |Set to `true` to actually store the field in the index, `false` to not
store it. Defaults to `false` (note, the JSON document itself is stored,
and it can be retrieved from it).
store it. Since by default ElasticSearch stores all fields of the source
document in the special `_source` field, this option is primarily useful when
the `_source` field has been disabled in the type definition. Defaults to
`false`.
|`index` |Set to `analyzed` for the field to be indexed and searchable
after being broken down into token using an analyzer. `not_analyzed`
@ -637,4 +639,3 @@ doesn't exist in existing documents.
Another important note is that new multi fields will be merged into the
list of existing multi fields, so when adding new multi fields for a field
previous added multi fields don't need to be specified.