-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
elastic should trace the response even http status code is not 2xx #297
Comments
I'll investigate if I can change |
I believe the issue I'm having is the same. I had a scroll request that would return an error on:
Which I then use to panic. The panic takes place because the response is a
I ended up using the trace output of the request to send a curl request. It's response included the additional detail I needed:
Adding |
Sorry! I didn't see the separate issue. Good to know about type checking Anyway, thanks for the awesome library. I'm enjoying it much more than official Python library. |
Closing for it is too old. If you still see this as a problem, please file a new issue and link back to this one. Thanks. |
Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[ ] elastic.v2 (for Elasticsearch 1.x)
[X] elastic.v3 (for Elasticsearch 2.x)
Please describe the expected behavior
elastic should trace the response even the http status code is not 2xx.
Please describe the actual behavior
I want to find specific doc by it's id, this doc doesn't exist in ES, then elastic returned an error with status code 401. I set trace log for elastic and try to figure out what happened, but I can't see the corresponding http response in trace log.
Any steps to reproduce the behavior?
Try to find an not exist doc by it's id
The text was updated successfully, but these errors were encountered: