Thanks, Yonik.
When the shards parameter is specified in a json facet query with the
stream method, it is still ordered by the count by default.
From our perf. test with totally 100,000,000 docs, the stream method is
the best and the enum method does not work for the field faceting.
I saw JSON Facet API is in your blog. When will be it officially
published and documented? Any schedule about it?
Thanks
在 2015/10/23 22:38, Yonik Seeley 写道:
On Fri, Oct 23, 2015 at 10:24 AM, Shalin Shekhar Mangar
wrote:
Now I am curious, what does it do!
It's basically like facet.method=enum, but it truly streams
(calculates each facet bucket on-the-fly and writes it to the
response).
Since it is streaming, it only supports sorting by term index order.
Although if there is need/demand, we could also do a lightweight
ordering over the buckets first (ordering by count or other facet
function) and then still stream, creating the buckets and any
sub-facets on the fly.
-Yonik
On Fri, Oct 23, 2015 at 7:40 PM, Yonik Seeley wrote:
On Fri, Oct 23, 2015 at 5:55 AM, hao jin wrote:
Hi
I found when the method of json facet is set to stream, the "missing" is not
added to the result.
Is it designed or a known issue?
You found an undocumented feature (method=stream) ;-)
That facet method doesn't have adequate testing yet, so I haven't
publicized / documented it.
Support for things like "missing" may be some of the stuff still TBD.
-Yonik
--
Regards,
Shalin Shekhar Mangar.
