-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Update delete-by-query.asciidoc #37370
Conversation
Pinging @elastic/es-core-features |
@@ -384,7 +384,7 @@ POST _tasks/r1A2WoRbTwKZ516z6NEs5A:36619/_cancel | |||
The task ID can be found using the <<tasks,tasks API>>. | |||
|
|||
Cancellation should happen quickly but might take a few seconds. The task status | |||
API above will continue to list the task until it is wakes to cancel itself. | |||
API above will continue to list the task until the task is awaken to cancel itself. |
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.
Perhaps something like the following?
API above will continue to list the task until the task is awaken to cancel itself. | |
API above will continue to list the task until the task awakens to cancel itself. |
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.
Well, does the task awaken by itself ? And it wasn't clear for me which task is canceled: the _delete_by_query
task or the cancel the _delete_by_query
task... Perhaps the text could be explicit to avoid ambiguities.
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.
which task is awaken *
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.
Well, does the task awaken by itself?
Technically the task checks periodically to see whether it has been cancelled, and if so, stops executing.
And it wasn't clear for me which task is canceled: the _delete_by_query task or the cancel the _delete_by_query task... Perhaps the text could be explicit to avoid ambiguities.
The delete-by-query task is the one that stops when cancelled (with the check I mentioned above).
Perhaps we should clarify it to something like
"Cancellation should happen quickly but might take a few seconds. The task static API will continue to list the task until the delete by query task checks that it has been cancelled and terminates itself."
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.
Technically the task checks periodically to see whether it has been cancelled, and if so, stops executing.
Nice!
Perhaps we should clarify it to something like
"Cancellation should happen quickly but might take a few seconds. The task static API will continue to list the task until the delete by query task checks that it has been cancelled and terminates itself."
The task static API also lists the cancel task right ? What about:
"The task static API will continue to list the delete by query task until this task checks that it has been cancelled and terminates itself."
:)
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.
That sounds good to me 👍
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.
Commited the change in my branch, is it ok ?
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, will merge this shortly, thanks!
Tried my best to clarify sentence on `_delete_by_query` docs.
Tried my best to clarify sentence on `_delete_by_query` docs.
Tried my best to clarify sentence on `_delete_by_query` docs.
Similar fix as elastic#37370.
Tried my best to clarify sentence on
_delete_by_query
docs.