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

Update delete-by-query.asciidoc #37370

Merged
merged 3 commits into from
Jan 15, 2019
Merged

Update delete-by-query.asciidoc #37370

merged 3 commits into from
Jan 15, 2019

Conversation

niloct
Copy link
Contributor

@niloct niloct commented Jan 11, 2019

Tried my best to clarify sentence on _delete_by_query docs.

@colings86 colings86 added >docs General docs changes :Data Management/Indices APIs APIs to create and manage indices and templates labels Jan 14, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@jakelandis jakelandis requested a review from dakrone January 14, 2019 15:31
@@ -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.
Copy link
Member

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?

Suggested change
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.

Copy link
Contributor Author

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

which task is awaken *

Copy link
Member

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."

Copy link
Contributor Author

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."

:)

Copy link
Member

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 👍

Copy link
Contributor Author

@niloct niloct Jan 14, 2019

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 ?

Copy link
Member

@dakrone dakrone left a 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!

@dakrone dakrone merged commit d435b03 into elastic:6.5 Jan 15, 2019
dakrone pushed a commit that referenced this pull request Jan 15, 2019
Tried my best to clarify sentence on `_delete_by_query` docs.
dakrone pushed a commit that referenced this pull request Jan 15, 2019
Tried my best to clarify sentence on `_delete_by_query` docs.
dakrone pushed a commit that referenced this pull request Jan 15, 2019
Tried my best to clarify sentence on `_delete_by_query` docs.
niloct added a commit to niloct/elasticsearch that referenced this pull request Jan 16, 2019
cbuescher pushed a commit that referenced this pull request Jan 24, 2019
cbuescher pushed a commit that referenced this pull request Jan 24, 2019
cbuescher pushed a commit that referenced this pull request Jan 24, 2019
cbuescher pushed a commit that referenced this pull request Jan 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates >docs General docs changes v6.5.5 v6.6.1 v6.7.0 v7.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants