-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Implement Delete-by-Query operation after Reshard #125519
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
Open
ankikuma
wants to merge
8
commits into
elastic:main
Choose a base branch
from
ankikuma:03182025/ReshardDeleteByQuery
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+10
−2
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
1e7cf9d
Make ShardSplittingQuery public
ankikuma 68794da
Merge remote-tracking branch 'upstream/main' into 03182025/ReshardDel…
ankikuma 233cea9
commit
ankikuma 1d08147
flush
ankikuma 3c6cdc6
Merge remote-tracking branch 'upstream/main' into 03182025/ReshardDel…
ankikuma 86c9a46
refresh branch
ankikuma 393ca7e
remove print
ankikuma b7814c6
Merge remote-tracking branch 'upstream/main' into 03182025/ReshardDel…
ankikuma File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think we can probably do this in stateless and avoid the need to publish this API here while we're incubating.
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.
also I'd probably move the flush/commit out of the delete operation itself and let something higher up decide when it needs to schedule those.
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.
Ah, indexWriter is private, sorry.
It's interesting that this works, given
InternalEngine.createWriter
creates anAssertingIndexWriter
in test, which is meant to throw whendeleteDocuments
is called. I'm guessing that not throwing on the query-taking variant ofdeleteDocuments
was an oversight.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.
By the way, I don't know if the flush and commit at this level is sufficient to allow us to move the split on this shard to DONE. When we do that, we're also going to drop the search filter for unowned documents, which means the search nodes need to be using the state we've just flushed. I think that implies we should be doing a refresh.