uboness f3c6108b71 introduced support for "shard_size" for terms & terms_stats facets. The "shard_size" is the number of term entries each shard will send back to the coordinating node. "shard_size" > "size" will increase the accuracy (both in terms of the counts associated with each term and the terms that will actually be returned the user) - of course, the higher "shard_size" is, the more expensive the processing becomes as bigger queues are maintained on a shard level and larger lists are streamed back from the shards. ...

closes #3821

2013-10-02 22:02:00 +02:00

..

date-histogram-facet.asciidoc

Migrated documentation into the main repo

2013-08-29 01:24:34 +02:00

filter-facet.asciidoc

Migrated documentation into the main repo

2013-08-29 01:24:34 +02:00

geo-distance-facet.asciidoc

Add distance supported units

2013-09-17 14:21:45 +02:00

histogram-facet.asciidoc

Migrated documentation into the main repo

2013-08-29 01:24:34 +02:00

query-facet.asciidoc

Migrated documentation into the main repo

2013-08-29 01:24:34 +02:00

range-facet.asciidoc

Migrated documentation into the main repo

2013-08-29 01:24:34 +02:00

statistical-facet.asciidoc

Migrated documentation into the main repo

2013-08-29 01:24:34 +02:00

terms-facet.asciidoc

introduced support for "shard_size" for terms & terms_stats facets. The "shard_size" is the number of term entries each shard will send back to the coordinating node. "shard_size" > "size" will increase the accuracy (both in terms of the counts associated with each term and the terms that will actually be returned the user) - of course, the higher "shard_size" is, the more expensive the processing becomes as bigger queues are maintained on a shard level and larger lists are streamed back from the shards.

2013-10-02 22:02:00 +02:00

terms-stats-facet.asciidoc

introduced support for "shard_size" for terms & terms_stats facets. The "shard_size" is the number of term entries each shard will send back to the coordinating node. "shard_size" > "size" will increase the accuracy (both in terms of the counts associated with each term and the terms that will actually be returned the user) - of course, the higher "shard_size" is, the more expensive the processing becomes as bigger queues are maintained on a shard level and larger lists are streamed back from the shards.

2013-10-02 22:02:00 +02:00