By default, if no pipe is specified, EQL will return return matchings from the tail, end of the stream,  not the front. The results are returned in ascending order.

(cherry picked from commit 2f50423)

By default, if no pipe is specified, EQL return results from the tail,
end of the stream,  not the front. The results are returned in ascending
 order.

(cherry picked from commit 2f50423)
(cherry picked from commit 946b0ac)
(cherry picked from commit 3382f36)

We were previously using what is effectively `results | head` to
retrieve the desired amount of results. The default behavior was changed
in elastic/elasticsearch#66387, which caused these tests to fail as
different results were returned over such a large dataset.

…87254)

* Re-enable test skipped due to temporary failure

This failure may still be present/intermittent, but it passes reliably
locally; trying again on CI to check status.

* Triggering build

This should fail on the latest snapshot

* Update EQL integration tests to reflect new default pipe

We were previously using what is effectively `results | head` to
retrieve the desired amount of results. The default behavior was changed
in elastic/elasticsearch#66387, which caused these tests to fail as
different results were returned over such a large dataset.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

…lastic#87254)

* Re-enable test skipped due to temporary failure

This failure may still be present/intermittent, but it passes reliably
locally; trying again on CI to check status.

* Triggering build

This should fail on the latest snapshot

* Update EQL integration tests to reflect new default pipe

We were previously using what is effectively `results | head` to
retrieve the desired amount of results. The default behavior was changed
in elastic/elasticsearch#66387, which caused these tests to fail as
different results were returned over such a large dataset.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

…lastic#87254)

* Re-enable test skipped due to temporary failure

This failure may still be present/intermittent, but it passes reliably
locally; trying again on CI to check status.

* Triggering build

This should fail on the latest snapshot

* Update EQL integration tests to reflect new default pipe

We were previously using what is effectively `results | head` to
retrieve the desired amount of results. The default behavior was changed
in elastic/elasticsearch#66387, which caused these tests to fail as
different results were returned over such a large dataset.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

…87254) (#87397)

* Re-enable test skipped due to temporary failure

This failure may still be present/intermittent, but it passes reliably
locally; trying again on CI to check status.

* Triggering build

This should fail on the latest snapshot

* Update EQL integration tests to reflect new default pipe

We were previously using what is effectively `results | head` to
retrieve the desired amount of results. The default behavior was changed
in elastic/elasticsearch#66387, which caused these tests to fail as
different results were returned over such a large dataset.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

…87254) (#87396)

* Re-enable test skipped due to temporary failure

This failure may still be present/intermittent, but it passes reliably
locally; trying again on CI to check status.

* Triggering build

This should fail on the latest snapshot

* Update EQL integration tests to reflect new default pipe

We were previously using what is effectively `results | head` to
retrieve the desired amount of results. The default behavior was changed
in elastic/elasticsearch#66387, which caused these tests to fail as
different results were returned over such a large dataset.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>