Skip to content

Conversation

@martijnvg
Copy link
Member

and the other way around.

Backporting #126640

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

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.19.0 labels Apr 11, 2025
@martijnvg martijnvg changed the title [9.0] Allow a tsdb data stream to rolled over to a logsdb data stream [8.x] Allow a tsdb data stream to rolled over to a logsdb data stream Apr 11, 2025
@martijnvg martijnvg removed the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Apr 11, 2025
@martijnvg martijnvg enabled auto-merge (squash) April 11, 2025 16:56
@martijnvg martijnvg disabled auto-merge April 12, 2025 08:04
@martijnvg martijnvg merged commit f16f4ce into elastic:8.x Apr 12, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant