-
Notifications
You must be signed in to change notification settings - Fork 25.4k
[ML] Prevent retention classes from failing when deleting documents in read-only indices #125408
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
[ML] Prevent retention classes from failing when deleting documents in read-only indices #125408
Conversation
Pinging @elastic/ml-core (Team:ML) |
Hi @valeriy42, I've created a changelog YAML for you. |
…olver for improved index handling
…b.com/valeriy42/elasticsearch into enhancement/1532-unused-stats-remover
…enhancement/1532-unused-stats-remover
@@ -31,6 +31,7 @@ abstract class AbstractExpiredJobDataRemover implements MlDataRemover { | |||
this.client = client; | |||
this.jobIterator = jobIterator; | |||
this.parentTaskId = parentTaskId; | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…managing writable indices
…enhancement/1532-unused-stats-remover
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 10 out of 10 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
docs/changelog/125408.yaml:2
- Typo detected: 'UnusuedStatsRemover' should be corrected to 'UnusedStatsRemover'.
summary: Prevent `UnusuedStatsRemover` from failing when deleting documents in read-only indices
…b.com/valeriy42/elasticsearch into enhancement/1532-unused-stats-remover
…mover' into enhancement/1532-unused-stats-remover
.../ml/src/main/java/org/elasticsearch/xpack/ml/job/retention/ExpiredModelSnapshotsRemover.java
Outdated
Show resolved
Hide resolved
.../ml/src/main/java/org/elasticsearch/xpack/ml/job/retention/ExpiredModelSnapshotsRemover.java
Show resolved
Hide resolved
💔 Backport failed
You can use sqren/backport to manually backport by running |
…n read-only indices (elastic#125408) Classes like UnusedStatsRemover delete orphaned documents without an associated job. When the indices are made read-only it will start failing as read-only means no delete. This PR ensures that the non-writable indices are not included in the delete-by-query requests. (cherry picked from commit c822a57)
…n read-only indices (elastic#125408) Classes like UnusedStatsRemover delete orphaned documents without an associated job. When the indices are made read-only it will start failing as read-only means no delete. This PR ensures that the non-writable indices are not included in the delete-by-query requests. (cherry picked from commit c822a57)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…n read-only indices (elastic#125408) Classes like UnusedStatsRemover delete orphaned documents without an associated job. When the indices are made read-only it will start failing as read-only means no delete. This PR ensures that the non-writable indices are not included in the delete-by-query requests. (cherry picked from commit c822a57)
…ments in read-only indices (#125408) (#128748) * [ML] Prevent retention classes from failing when deleting documents in read-only indices (#125408) Classes like UnusedStatsRemover delete orphaned documents without an associated job. When the indices are made read-only it will start failing as read-only means no delete. This PR ensures that the non-writable indices are not included in the delete-by-query requests. (cherry picked from commit c822a57) * [CI] Auto commit changes from spotless * fit build failure --------- Co-authored-by: elasticsearchmachine <[email protected]>
…ents in read-only indices (#125408) (#128747) * [ML] Prevent retention classes from failing when deleting documents in read-only indices (#125408) Classes like UnusedStatsRemover delete orphaned documents without an associated job. When the indices are made read-only it will start failing as read-only means no delete. This PR ensures that the non-writable indices are not included in the delete-by-query requests. (cherry picked from commit c822a57) * [CI] Auto commit changes from spotless * fit build failure --------- Co-authored-by: elasticsearchmachine <[email protected]>
…ments in read-only indices (#125408) (#128749) * [ML] Prevent retention classes from failing when deleting documents in read-only indices (#125408) Classes like UnusedStatsRemover delete orphaned documents without an associated job. When the indices are made read-only it will start failing as read-only means no delete. This PR ensures that the non-writable indices are not included in the delete-by-query requests. (cherry picked from commit c822a57) * [CI] Auto commit changes from spotless * fit build failure --------- Co-authored-by: elasticsearchmachine <[email protected]>
Classes like UnusedStatsRemover delete orphaned documents without an associated job. When the indices are made read-only it will start failing as read-only means no delete.
This PR ensures that the non-writable indices are not included in the delete-by-query requests.