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

Remove the failures field from snapshot responses #114496

Merged
merged 16 commits into from
Feb 5, 2025

Conversation

arteam
Copy link
Contributor

@arteam arteam commented Oct 10, 2024

Failure handling for snapshots was made stricter in #107191 (8.15), so this field is always empty since then. Clients don't need to check it anymore for failure handling, we can remove it from API responses in 9.0

Failure handling for snapshots was made stricter in elastic#107191 (8.15),
so this field is always empty since then. Clients don't need to check it
anymore for failure handling, we can remove it from API responses in 9.0
@arteam arteam added WIP :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs labels Oct 10, 2024
@arteam arteam marked this pull request as ready for review October 16, 2024 08:07
@arteam arteam requested review from original-brownbear and DaveCTurner and removed request for original-brownbear October 16, 2024 08:07
@arteam arteam added >non-issue and removed WIP labels Oct 17, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Oct 17, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

@arteam arteam added >refactoring and removed Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. labels Oct 17, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Oct 17, 2024
@nicktindall
Copy link
Contributor

Happy to re-review once bwc stuff is in place!

@arteam
Copy link
Contributor Author

arteam commented Oct 24, 2024

@elasticmachine update branch

@arteam arteam requested review from nicktindall and removed request for nicktindall October 24, 2024 18:34
Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather we fixed up the transport protocol at the same time here rather than leaving a // TODO comment in the code. Let's delay this until v9 has its own transport version.

@elasticsearchmachine elasticsearchmachine added v9.1.0 Team:Distributed Coordination Meta label for Distributed Coordination team and removed v9.0.0 labels Jan 30, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed-obsolete (Team:Distributed (Obsolete))

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

@arteam arteam force-pushed the remove-snapshot-failures branch from 81fef7e to 7ecfe8f Compare February 4, 2025 08:10
@arteam arteam requested a review from DaveCTurner February 5, 2025 11:01
Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. It's vital that this is backported to 9.0.

@arteam arteam added auto-backport Automatically create backport pull requests when merged v9.0.1 labels Feb 5, 2025
@arteam arteam added v9.0.0 and removed v9.0.0 labels Feb 5, 2025
@arteam arteam merged commit 62f0fe8 into elastic:main Feb 5, 2025
17 checks passed
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
9.0 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 114496

arteam added a commit to arteam/elasticsearch that referenced this pull request Feb 5, 2025
…4496)

Backports elastic#114496 to 9.0

> Failure handling for snapshots was made stricter in elastic#107191 (8.15), so this
field is always empty since then. Clients don't need to check it anymore for
failure handling, we can remove it from API responses in 9.0
@arteam arteam deleted the remove-snapshot-failures branch February 5, 2025 15:03
arteam added a commit that referenced this pull request Feb 5, 2025
…121770)

Backports #114496 to 9.0

> Failure handling for snapshots was made stricter in #107191 (8.15), so this
field is always empty since then. Clients don't need to check it anymore for
failure handling, we can remove it from API responses in 9.0
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 backport pending :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >non-issue >refactoring Team:Distributed Coordination Meta label for Distributed Coordination team Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. v9.0.1 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants