Skip to content

[DOCS] Relocate index.mapping.dimension_fields.limit setting docs #80964

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 1 commit into from
Nov 23, 2021
Merged

[DOCS] Relocate index.mapping.dimension_fields.limit setting docs #80964

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
16 changes: 0 additions & 16 deletions docs/reference/index-modules.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -329,22 +329,6 @@ indicates no ingest pipeline will run.
NOTE: You can't use a final pipeline to change the `_index` field. If the
pipeline attempts to change the `_index` field, the indexing request will fail.

[[index-mapping-dimension-fields-limit]]
`index.mapping.dimension_fields.limit`::
+
--
experimental:[]

.For internal use by Elastic only.
[%collapsible]
====
Maximum number of time series dimensions for the index. Defaults to `16`.

You can mark a field as a dimension using the `time_series_dimension` mapping
parameter.
====
--

[[index-hidden]] `index.hidden`::

Indicates whether the index should be hidden by default. Hidden indices are not
Expand Down
16 changes: 16 additions & 0 deletions docs/reference/mapping/mapping-settings-limit.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,3 +47,19 @@ If your field mappings contain a large, arbitrary set of keys, consider using th
It usually shouldn't be necessary to set this setting. The default is okay
unless a user starts to add a huge number of fields with really long names. Default is
`Long.MAX_VALUE` (no limit).

[[index-mapping-dimension-fields-limit]]
`index.mapping.dimension_fields.limit`::
+
--
experimental:[] (<<dynamic-index-settings,Dynamic>>, integer)

.For internal use by Elastic only.
[%collapsible]
====
Maximum number of time series dimensions for the index. Defaults to `16`.

You can mark a field as a dimension using the `time_series_dimension` mapping
parameter.
====
--