Skip to content

[8.15] [DOCS][101] Update first quick start with mappings examples (#113558) #113973

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 3, 2024
Merged

[8.15] [DOCS][101] Update first quick start with mappings examples (#113558) #113973

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b35ec14
[DOCS][101] Update first quick start with mappings examples (#113558)
leemthompo Oct 2, 2024
256a4e7
Fix broken link
leemthompo Oct 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion docs/reference/mapping.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,9 +75,29 @@ reindexing. You can use runtime fields in conjunction with indexed fields to
balance resource usage and performance. Your index will be smaller, but with
slower search performance.

[discrete]
[[mapping-manage-update]]
== Managing and updating mappings

Explicit mappings should be defined at index creation for fields you know in advance.
You can still add _new fields_ to mappings at any time, as your data evolves.

Use the <<indices-put-mapping,Update mapping API>> to update an existing mapping.

In most cases, you can't change mappings for fields that are already mapped.
These changes require <<docs-reindex,reindexing>>.

However, you can _update_ mappings under certain conditions:

* You can add new fields to an existing mapping at any time, explicitly or dynamically.
* You can add new <<multi-fields,multi-fields>> for existing fields.
** Documents indexed before the mapping update will not have values for the new multi-fields until they are updated or reindexed. Documents indexed after the mapping change will automatically have values for the new multi-fields.
* Some <<mapping-params,mapping parameters>> can be updated for existing fields of certain <<mapping-types,data types>>.

[discrete]
[[mapping-limit-settings]]
== Settings to prevent mapping explosion
== Prevent mapping explosions

Defining too many fields in an index can lead to a mapping explosion, which can
cause out of memory errors and difficult situations to recover from.

Expand Down
Loading