-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
MultiSearch fail to work with raw json #705
Comments
Can you send a working sample of your code so that I can reproduce? |
I just took the exisiting msearch_test.go and modified to reproduce the issue. Please find below. I am not sure if I am passing raw json with right API. Let me know.
|
The problem might be here - Line 71 in a7f6620
|
Thanks. I could reproduce the issue and there's a fix in the next release. I hope to get it out this weekend. |
Super, thanks for fixing it quickly. -Karthik |
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)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ * ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
Please describe the expected behavior
Does multisearch accept raw json for each elastic search request?
Please describe the actual behavior
I am using multisearch request containing each elastic search request with raw json and index to operate on. I am getting error from elastic search as - "elastic: Error 400 (Bad Request): Expcted [START_OBJECT] but found [VALUE_STRING] [type=parsing_exeception".
Any steps to reproduce the behavior?
The text was updated successfully, but these errors were encountered: