: When shooting a distributed query, we use facet.limit=1000. Then the merging
: SOLR combines the results. We also use facet.zeros=false to ensure returning
: only non-zero facet entries.
: The issue that we found is that there was a gap in time in the final results
: list (reverse sorted by date attached to each entry in all the shards),
: whereby entries stamped with certain date disappeared. If we use different
: query criteria, that produces less than 1000 results both in each of the
: shards and combined, we see those "missing" entries. So the problem is not
: in missing data, but in the combination algorithm.
I don't understand what you mean by "entries stamped with certain date"
... are you saying the actaul results of the search seem to be missing
documents, or that the fact counts returned seemed to be missing
constraints that should be in the list?
it seems like you are refering to documents missing from the actaul
results ("reverse sorted by date") but facet.limit can't affect anything
about the results of the actual query. facet.limit also only applies to
facet.field (not facet.date or facet.range), but you're talking about a
date field....
can you please be specific about the requests you are executing (ie: what
params) the schema you have (ie: what are the fields/types in use in all
the params/query strings), the results you are getting, and the results
you are expecting? actually providing the response xml is very helpful.
(change the "fl" to hide any fields you consider sensitive)
-Hoss
