This is contrived I admit, but let's say you have
a query with 100 hits with a score distribution of
1 doc with a score of 100
98 docs with a score of 91
1 doc with a score of 1
Now I get 99 docs in my results set. Next I delete the
doc that scored 1 and my returned doc set
_for the exact same que
Hi Joel,
Thanks for the pointer. Can you point me to any example implementation.
Parvesh Garg,
Founding Architect
http://www.zettata.com
On Tue, Oct 21, 2014 at 9:32 PM, Joel Bernstein wrote:
> The RankQuery cannot be used as filter. It is designed for custom
> ordering/ranking of results on
Hi Erick,
Thanks for the input. We have other requirements regarding precision and
recall, especially when other sorts are specified. So need to suppress docs
based on thresholds.
Parvesh Garg,
Founding Architect
http://www.zettata.com
On Tue, Oct 21, 2014 at 8:20 PM, Erick Erickson
wrote:
The RankQuery cannot be used as filter. It is designed for custom
ordering/ranking of results only. If it's used as filter the facet counts
will not match up. If you need a filter collector then you need to use a
PostFilter.
Joel Bernstein
Search Engineer at Heliosearch
On Tue, Oct 21, 2014 at 10
I _very strongly_ recommend that you do _not_ do this.
First, the "problem" of having documents in the results
list with, say, scores < 20% of the max takes care of itself;
users stop paging pretty quickly. You're arbitrarily
denying the users any chance of finding some documents
that _do_ match t
Hi All,
We have written a RankQuery plugin with a custom TopDocsCollector to
suppress documents below a certain threshold w.r.t. to the maxScore for
that query. It works fine and is reflected well with numFound and start
parameters.
Our problem lies with facet counts. Even though the docs numFoun
