I like the FieldSortedHitQueue idea. If you want to work up a patch for
that, it would be great.
Joel Bernstein
Search Engineer at Heliosearch
On Wed, Jul 23, 2014 at 5:17 PM, Peter Keegan
wrote:
> > The ReRankingQParserPlugin uses the Lucene QueryRescorer, which only uses
> the score from th
> The ReRankingQParserPlugin uses the Lucene QueryRescorer, which only uses
the score from the re-rank query when re-ranking the top N documents.
Understood, but if the re-rank scores produce new ties, wouldn't you want
to resort them with the FieldSortedHitQueue?
Anyway, I was looking to reimple
Blog on the RankQuery API
http://heliosearch.org/solrs-new-rankquery-feature/
Joel Bernstein
Search Engineer at Heliosearch
On Wed, Jul 23, 2014 at 3:27 PM, Joel Bernstein wrote:
> The ReRankingQParserPlugin uses the Lucene QueryRescorer, which only uses
> the score from the re-rank query when
The ReRankingQParserPlugin uses the Lucene QueryRescorer, which only uses
the score from the re-rank query when re-ranking the top N documents.
The ReRanklingQParserPlugin is built as a RankQuery plugin so you can swap
in your own implementation. Patches are also welcome for the existing
implement
See http://heliosearch.org/solrs-new-re-ranking-feature/
On Wed, Jul 23, 2014 at 11:27 AM, Erick Erickson
wrote:
> I'm having a little trouble understanding the use-case here. Why use
> re-ranking?
> Isn't this just combining the original query with the second query with an
> AND
> and using th
I'm having a little trouble understanding the use-case here. Why use
re-ranking?
Isn't this just combining the original query with the second query with an
AND
and using the original sort?
At the end, you have your original list in it's original order, with
(potentially) some
documents removed tha
