Remove terms API


(Shay Banon) #1

Hi,

I am considering removing the terms API from elasticsearch. This is for
the simple reason that with the new facets provided, the terms API is
actually a subset of a search request (with a query to match all documents
and a size of 0), with facets providing much more functionality. Any
additional functionality can be provided in the facets area, and I prefer
not to maintain an API that in any case the search API is probably a better
fit for. What do you think?

Also, there is an issue to provide facets for count API as well. This is
another case of a subset of the search API with size set to 0, with the
search API providing much more options.

If there are no objections, I will remove it in a week or so before
releasing version 0.9.

-shay.banon


(tfreitas) #2

+1
good for me

On Jun 25, 3:44 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Hi,

I am considering removing the terms API from elasticsearch. This is for
the simple reason that with the new facets provided, the terms API is
actually a subset of a search request (with a query to match all documents
and a size of 0), with facets providing much more functionality. Any
additional functionality can be provided in the facets area, and I prefer
not to maintain an API that in any case the search API is probably a better
fit for. What do you think?

Also, there is an issue to provide facets for count API as well. This is
another case of a subset of the search API with size set to 0, with the
search API providing much more options.

If there are no objections, I will remove it in a week or so before
releasing version 0.9.

-shay.banon


(Lukáš Vlček) #3

+1
Lukas

On Fri, Jun 25, 2010 at 9:44 PM, Shay Banon shay.banon@elasticsearch.comwrote:

Hi,

I am considering removing the terms API from elasticsearch. This is for
the simple reason that with the new facets provided, the terms API is
actually a subset of a search request (with a query to match all documents
and a size of 0), with facets providing much more functionality. Any
additional functionality can be provided in the facets area, and I prefer
not to maintain an API that in any case the search API is probably a better
fit for. What do you think?

Also, there is an issue to provide facets for count API as well. This is
another case of a subset of the search API with size set to 0, with the
search API providing much more options.

If there are no objections, I will remove it in a week or so before
releasing version 0.9.

-shay.banon


(system) #4