Skip to content

Commit

Permalink
Docs: Detail on false/strict dynamic mapping setting (#22451)
Browse files Browse the repository at this point in the history
  • Loading branch information
veatch authored and nik9000 committed Jan 5, 2017
1 parent 4f97027 commit e7e1744
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion docs/reference/mapping/dynamic/field-mapping.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,8 @@
By default, when a previously unseen field is found in a document,
Elasticsearch will add the new field to the type mapping. This behaviour can
be disabled, both at the document and at the <<object,`object`>> level, by
setting the <<dynamic,`dynamic`>> parameter to `false` or to `strict`.
setting the <<dynamic,`dynamic`>> parameter to `false` (to ignore new fields) or to `strict` (to throw
an exception if an unknown field is encountered).

Assuming `dynamic` field mapping is enabled, some simple rules are used to
determine which datatype the field should have:
Expand Down

0 comments on commit e7e1744

Please sign in to comment.