asyncSearch get returns irrelevant results

[lizozom]

There's an issue with the implementation of the elasticsearch client's asyncSearch.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.

[delvedor]

Hello! Can you please create a snippet of code that just uses the client that reproduces the issue?

[stale]

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.
It will be closed if no further activity occurs, please write a comment if you would like to keep this going.

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

[lizozom]

I just created a PR to use the new asyncSearch endpoints, so I'm closing the issue.

The problem was that due to a badly formatted request, I was running a "SELECT ALL" query.
Coincidentally, data from the .async-search index is returned first, resulting in this weird behavior.
As soon as I fixed the query, everything works as expected.