Skip to content

Commit 20f9017

Browse files
veatchnik9000
authored andcommitted
Docs: Detail on false/strict dynamic mapping setting (#22451)
Reference: https://www.elastic.co/guide/en/elasticsearch/guide/master/dynamic-mapping.html
1 parent 5daf462 commit 20f9017

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/reference/mapping/dynamic/field-mapping.asciidoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,8 @@
44
By default, when a previously unseen field is found in a document,
55
Elasticsearch will add the new field to the type mapping. This behaviour can
66
be disabled, both at the document and at the <<object,`object`>> level, by
7-
setting the <<dynamic,`dynamic`>> parameter to `false` or to `strict`.
7+
setting the <<dynamic,`dynamic`>> parameter to `false` (to ignore new fields) or to `strict` (to throw
8+
an exception if an unknown field is encountered).
89

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

0 commit comments

Comments
 (0)