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
Comments
Is there an API to check if there was a failure, something similar to BulkResponse.hasFailures? |
Hi @ssanghavi , via java API you can check the failures by iterating through the |
Any updates on getting this functionality through the REST response? I'm currently experiencing the same behavior. |
hi @kujenga as far as I can see the delete by query api now returns a failures |
@javanna got it, thanks. I'm seeing an empty |
@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? |
@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. |
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
The text was updated successfully, but these errors were encountered: