honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Explain mapping explosion (#25654)

This commit is contained in:
Antonio Matarrese 2017-07-14 08:47:41 +01:00 committed by Luca Cavanna
parent 9040f4498e
commit afd9a1c1b1
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/mapping.asciidoc
View File

@ -66,6 +66,14 @@ via the <<multi-fields>> parameter.
[float] [float]
=== Settings to prevent mappings explosion === Settings to prevent mappings explosion
Defining too many fields in an index is a condition that can lead to a
mapping explosion, which can cause out of memory errors and difficult
situations to recover from. This problem may be more common than expected.
As an example, consider a situation in which every new document inserted
introduces new fields. This is quite common with dynamic mappings.
Every time a document contains new fields, those will end up in the index's
mappings. This isn't worrying for a small amount of data, but it can become a
problem as the mapping grows.
The following settings allow you to limit the number of field mappings that The following settings allow you to limit the number of field mappings that
can be created manually or dynamically, in order to prevent bad documents from can be created manually or dynamically, in order to prevent bad documents from
causing a mapping explosion: causing a mapping explosion: