Skip to content

Conversation

@masseyke
Copy link
Member

@masseyke masseyke commented Feb 3, 2025

In the reindex data streams code, we do not currently check whether every document has succeeded. A ReindexAction succeeds even if all documents fail. This means that we swap the potentially-empty destination index into the data stream, and then delete the source index containing data that was not moved over to the destination index. This PR changes it so that the entire task fails if there are any failed documents, and the source index is not deleted.

@masseyke masseyke added >non-issue :Data Management/Data streams Data streams and their lifecycles auto-backport Automatically create backport pull requests when merged v9.0.0 v8.18.0 v8.19.0 v9.1.0 labels Feb 3, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label Feb 3, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@masseyke masseyke merged commit c77afd8 into elastic:main Feb 4, 2025
17 checks passed
@masseyke masseyke deleted the fail-data-stream-reindex-if-any-document-fails branch February 4, 2025 15:36
masseyke added a commit to masseyke/elasticsearch that referenced this pull request Feb 4, 2025
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
9.0
8.18
8.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged :Data Management/Data streams Data streams and their lifecycles >non-issue Team:Data Management Meta label for data/management team v8.18.0 v8.19.0 v9.0.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants