-
Notifications
You must be signed in to change notification settings - Fork 727
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
Can't use asStream with body on v8 but docs say we can #2241
Comments
#2241 notes that there is no body attribute on a response. This is mostly just a typo in the example, as `result` itself is a readable stream, unless `meta: true` is passed, in which case `result.body` will be a readable stream. Also dropped the callback-style stream processing example as it's a bit outdated.
Thanks for the question @tomimarkus991. I think the issue here is that the code example was a bit confusing, as I updated the code example in #2242 to make that more clear. I was able to run the updated code snippet verbatim against a local 8.13.0 Elasticsearch instance and it worked perfectly. |
thanks alot |
#2241 notes that there is no body attribute on a response. This is mostly just a typo in the example, as `result` itself is a readable stream, unless `meta: true` is passed, in which case `result.body` will be a readable stream. Also dropped the callback-style stream processing example as it's a bit outdated.
#2241 notes that there is no body attribute on a response. This is mostly just a typo in the example, as `result` itself is a readable stream, unless `meta: true` is passed, in which case `result.body` will be a readable stream. Also dropped the callback-style stream processing example as it's a bit outdated. (cherry picked from commit 45e3c06)
#2241 notes that there is no body attribute on a response. This is mostly just a typo in the example, as `result` itself is a readable stream, unless `meta: true` is passed, in which case `result.body` will be a readable stream. Also dropped the callback-style stream processing example as it's a bit outdated. (cherry picked from commit 45e3c06)
#2241 notes that there is no body attribute on a response. This is mostly just a typo in the example, as `result` itself is a readable stream, unless `meta: true` is passed, in which case `result.body` will be a readable stream. Also dropped the callback-style stream processing example as it's a bit outdated. (cherry picked from commit 45e3c06) Co-authored-by: Josh Mock <[email protected]>
#2241 notes that there is no body attribute on a response. This is mostly just a typo in the example, as `result` itself is a readable stream, unless `meta: true` is passed, in which case `result.body` will be a readable stream. Also dropped the callback-style stream processing example as it's a bit outdated. (cherry picked from commit 45e3c06) Co-authored-by: Josh Mock <[email protected]>
Elasticsearch Version
v8.13
Installed Plugins
@elastic/elasticsearch
Java Version
bundled
OS Version
Darwin ip-192-168-0-21.eu-north-1.compute.internal 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000 arm64
Problem Description
https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/8.13/as_stream_examples.html
Docs say to use body but there is no body on result.
using regular payload is not working
Steps to Reproduce
try to add asStream to search and use body.
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: