Exists API: Allow user to find if any document exists for a given query #6995
Assignees
Labels
Comments
areek
added a commit
to areek/elasticsearch
that referenced
this issue
Jul 31, 2014
… query Implements a new Exists API allowing users to do fast exists check on any matched documents for a given query. This API should be faster then using the Count API as it will: - early terminate the search execution once any document is found to exist - return the response as soon as the first shard reports matched documents closes elastic#6995
areek
added a commit
that referenced
this issue
Jul 31, 2014
… query Implements a new Exists API allowing users to do fast exists check on any matched documents for a given query. This API should be faster then using the Count API as it will: - early terminate the search execution once any document is found to exist - return the response as soon as the first shard reports matched documents closes #6995
areek
added a commit
that referenced
this issue
Sep 8, 2014
… query Implements a new Exists API allowing users to do fast exists check on any matched documents for a given query. This API should be faster then using the Count API as it will: - early terminate the search execution once any document is found to exist - return the response as soon as the first shard reports matched documents closes #6995
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
May 13, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The idea behind the new API is to enable fast exists functionality for documents, given a query. It would be very similar to the existing count API.
This API will be faster then using the Count API (setting terminate_after=1) in the general case, as it would return the response after the first shard reports existing documents, instead of blocking for responses from all the shards. In the worst case, if no documents actually exists, it would be as performant as using the Count API with terminate_after=1.
(Check corresponding PR for req/response)
related to #6876
The text was updated successfully, but these errors were encountered: