Skip to content

Conversation

@danhermann
Copy link
Contributor

If a naming conflict for a new write index is detected when a data stream rolls over, it will now increment its own generation until the new write index's name does not conflict with any other indices, aliases, or data streams. This allows us to remove the trappy validation around name conflicts for the backing indices of data streams.

Fixes #70905.

Backport of #70934

@elasticmachine elasticmachine added the Team:Data Management Meta label for data/management team label Mar 29, 2021
@elasticmachine
Copy link
Collaborator

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

@danhermann danhermann merged commit 71b476b into elastic:7.x Mar 29, 2021
@danhermann danhermann deleted the backport_7x_70934_simplify_ds_rollover branch March 29, 2021 15:10
danhermann added a commit to danhermann/elasticsearch that referenced this pull request Mar 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport :Data Management/Data streams Data streams and their lifecycles >enhancement Team:Data Management Meta label for data/management team v7.13.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants