-
Notifications
You must be signed in to change notification settings - Fork 725
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
asyncSearch get returns irrelevant results #1280
Comments
Hello! Can you please create a snippet of code that just uses the client that reproduces the issue? |
We understand that this might be important for you, but this issue has been automatically marked as stale because it has not had recent activity either from our end or yours. Note: in the past months we have built a new client, that has just landed in master. If you want to open an issue or a pr for the legacy client, you should do that in https://github.com/elastic/elasticsearch-js-legacy |
I just created a PR to use the new The problem was that due to a badly formatted request, I was running a "SELECT ALL" query. |
There's an issue with the implementation of the
elasticsearch
client'sasyncSearch.get
endpoint, that is used to fetch the data from a running async search.Instead of returning the data from the
asyncId
, it seems to return a list of unrelated async search IDs from the.async-search
index.This behavior can be reproduced by using this PR and going to discover.
Same code works correctly if I use the new ES client with a transport request, instead of the asyncSearch one.
The text was updated successfully, but these errors were encountered: