Add support for shard_size for terms & terms_stats facets

[darkwish121]

The higher the requested size is, the more accurate the results will be, but also, the more expensive it will be to compute the final results (both due to bigger priority queues that are managed on a shard level and due to bigger data transfers between the nodes and the client). In an attempt to minimize the extra work that comes with bigger requested size the shard_size parameter was introduced. When defined, it will determine how many terms the coordinating node will request from each shard. Once all the shards responded, the coordinating node will then reduce them to a final result which will be based on the size parameter - this way, one can increase the accuracy of the returned terms and avoid the overhead of streaming a big list of terms back to the client.

Note that shard_size cannot be smaller than size… if that’s the case elasticsearch will override it and reset it to be equal to size

[ruflin]

Does this only apply to Terms & Terms_stats facets or also to other?

Here for more details on the size and shard_size for Terms Facet: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-facets-terms-facet.html

[darkwish121]

Yes this is only apply to terms facet and terms stats facet

On Thu, Jul 10, 2014 at 3:45 PM, Nicolas Ruflin notifications@github.com
wrote:

Does this only apply to Terms & Terms_stats facets or also to other?

Here for more details on the size and shard_size for Terms Facet:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-facets-terms-facet.html

—
Reply to this email directly or view it on GitHub
#648 (comment).

[ruflin]

@darkwish121 Any time to open a pull request?

[im-denisenko]

Wontfix due to #855.

@darkwish121 Use $facet->setParam('shard_size', $size); instead.