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

Delete by query doesn't return failure reasons #5093

Closed
kzwang opened this issue Feb 12, 2014 · 7 comments
Closed

Delete by query doesn't return failure reasons #5093

kzwang opened this issue Feb 12, 2014 · 7 comments

Comments

@kzwang
Copy link
Contributor

kzwang commented Feb 12, 2014

If we run delete by query and there are some shards failed, we only got failed shards count but doesn't contains failure reasons

e.g. #5083

@ssanghavi
Copy link

Is there an API to check if there was a failure, something similar to BulkResponse.hasFailures?
This would help at least in logging when there is a failure ...

@javanna
Copy link
Member

javanna commented Feb 20, 2014

Hi @ssanghavi , via java API you can check the failures by iterating through the IndexDeleteByQueryResponse that you can retrieve through theDeleteByQueryResponse#getIndices method. What is missing is returning them in the rest response.

@kujenga
Copy link

kujenga commented Jun 26, 2017

Any updates on getting this functionality through the REST response? I'm currently experiencing the same behavior.

@javanna
Copy link
Member

javanna commented Jun 27, 2017

hi @kujenga as far as I can see the delete by query api now returns a failures array. My last comment is not valid anymore, in fact delete by query was completely rewritten since then.

@kujenga
Copy link

kujenga commented Jun 27, 2017

@javanna got it, thanks. I'm seeing an empty failures array but a non-zero number failure count indicated in the response, which sounded similar to this issue.

@nik9000
Copy link
Member

nik9000 commented Jun 28, 2017

@kujenga what version are you seeing this on? Anything before 5.0 is beyond my ability to comment on, but if it happens in 5.x we likely still have the bug so it is worth tracking down. Also, do you get any related logs?

@kujenga
Copy link

kujenga commented Jun 28, 2017

@nik9000 we're on 2.3, but it's good news that upgrading may improve this functionality. I'll dig through the logs to see if there's anything relevant 👍, thanks for the tip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants