Skip to content
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.

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

[7.x] Add prefer_v2_templates flag and index setting (#55411) #55476

Merged
merged 1 commit into from
Apr 20, 2020

Conversation

dakrone
Copy link
Member

@dakrone dakrone commented Apr 20, 2020

This commit adds a new querystring parameter on the following APIs:

  • Index
  • Update
  • Bulk
  • Create Index
  • Rollover

These APIs now support a ?prefer_v2_templates=true|false flag. This flag changes the preference
creation to use either V2 index templates or V1 templates. This flag defaults to false and will be
changed to true for 8.0+ in subsequent work.

Additionally, setting this flag internally sets the index.prefer_v2_templates index-level setting.
This setting is used so that actions that automatically create a new index (things like rollover
initiated by ILM) will inherit the preference from the original index. This setting is dynamic so
that a transition from v1 to v2 templates can occur for long-running indices grouped by an alias
performing periodic rollover.

This also adds support for sending this parameter to the High Level Rest Client.

Relates to #53101

This commit adds a new querystring parameter on the following APIs:
- Index
- Update
- Bulk
- Create Index
- Rollover

These APIs now support a `?prefer_v2_templates=true|false` flag. This flag changes the preference
creation to use either V2 index templates or V1 templates. This flag defaults to `false` and will be
changed to `true` for 8.0+ in subsequent work.

Additionally, setting this flag internally sets the `index.prefer_v2_templates` index-level setting.
This setting is used so that actions that automatically create a new index (things like rollover
initiated by ILM) will inherit the preference from the original index. This setting is dynamic so
that a transition from v1 to v2 templates can occur for long-running indices grouped by an alias
performing periodic rollover.

This also adds support for sending this parameter to the High Level Rest Client.

Relates to elastic#53101
@dakrone dakrone added :Data Management/Indices APIs APIs to create and manage indices and templates backport v7.8.0 labels Apr 20, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Indices APIs)

dakrone added a commit to dakrone/elasticsearch that referenced this pull request Apr 20, 2020
This adjusts the minimum version for serialization for elastic#55411.

It should only be merged after elastic#55476 has been merged
dakrone added a commit to dakrone/elasticsearch that referenced this pull request Apr 20, 2020
This disableds BWC for the backport of elastic#55411
Backport: elastic#55476
Version adjustment: elastic#55478
dakrone added a commit that referenced this pull request Apr 20, 2020
This disables BWC for the backport of #55411
Backport: #55476
Version adjustment: #55478
@dakrone dakrone merged commit 9eddd2b into elastic:7.x Apr 20, 2020
@dakrone dakrone deleted the backport/7.x/pr-55411 branch April 20, 2020 18:05
dakrone added a commit that referenced this pull request Apr 20, 2020
This adjusts the minimum version for serialization for #55411.

It should only be merged after #55476 has been merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Data Management/Indices APIs APIs to create and manage indices and templates v7.8.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants