Skip to content

Conversation

@martijnvg
Copy link
Member

and the other way around.

Backporting #126640 to 8.18 branch.

This doesn't make much sense. However, if a data stream's index mode differs from the index mode of most recent backing index, then this can cause confusion. Typically, misconfiguration is a reason this can happen.

Related to #126637

and the other way around.

Backporting elastic#126640 to 8.18 branch.

This doesn't make much sense. However, if a data stream's index mode differs from the index mode of most recent backing index, then this can cause confusion. Typically, misconfiguration is a reason this can happen.

Related to elastic#126637
@martijnvg martijnvg added backport auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) v8.18.1 labels Apr 11, 2025
@elasticsearchmachine elasticsearchmachine merged commit 8c439ff into elastic:8.18 Apr 11, 2025
15 checks passed
@martijnvg martijnvg deleted the backport_126640_8.18 branch April 11, 2025 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport v8.18.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants