Skip to content

HLRC: Add throttling for update & delete-by-query #33951

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

Merged
merged 4 commits into from
Oct 2, 2018

Conversation

cbuescher
Copy link
Member

This change adds throttling to the update-by-query and delete-by-query cases
similar to throttling for reindex. This mostly means additional methods on the
client class itself, since the request hits the same RestHandler, just with
slightly different endpoints, and also the return values are similar.
Also updating the docs to reflect this.

This change adds throttling to the update-by-query and delete-by-query cases
similar to throttling for reindex. This mostly means additional methods on the
client class itself, since the request hits the same RestHandler, just with
slightly different endpoints, and also the return values are similar.
Also updating the docs to reflect this.
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@cbuescher
Copy link
Member Author

@nik9000 this is largely analogous to #33832, sorry to bother you again with it but you should be most familiar with the API anyway

@cbuescher
Copy link
Member Author

@nik9000 thanks, I addressed your comment

@@ -855,6 +900,8 @@ public void testDeleteByQuery() throws IOException {
.source(Collections.singletonMap("foo", 1), XContentType.JSON))
.add(new IndexRequest(sourceIndex, "type", "2")
.source(Collections.singletonMap("foo", 2), XContentType.JSON))
.add(new IndexRequest(sourceIndex, "type", "3")
.source(Collections.singletonMap("foo", 3), XContentType.JSON))
Copy link
Member

Choose a reason for hiding this comment

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

You indent this differently than the thing above it.

Copy link
Member Author

Choose a reason for hiding this comment

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

Non-intentional indenting indeed. As penance I now will have to repeat this rapidly a couple of times. And will change of course.

@cbuescher
Copy link
Member Author

@nik9000 thanks for the review. I think I will not wait for another full CI run just because of the last re-indention commit but merge to master regardless.

@cbuescher cbuescher merged commit a1c441f into elastic:master Oct 2, 2018
cbuescher pushed a commit that referenced this pull request Oct 2, 2018
This change adds throttling to the update-by-query and delete-by-query cases
similar to throttling for reindex. This mostly means additional methods on the
client class itself, since the request hits the same RestHandler, just with
slightly different endpoints, and also the return values are similar.
kcm pushed a commit that referenced this pull request Oct 30, 2018
This change adds throttling to the update-by-query and delete-by-query cases
similar to throttling for reindex. This mostly means additional methods on the
client class itself, since the request hits the same RestHandler, just with
slightly different endpoints, and also the return values are similar.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants