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 implementation. Joel Bernstein Search Engineer at Heliosearch On Wed, Jul 23, 2014 at 11:37 AM, Peter Keegan <peterlkee...@gmail.com> wrote: > See http://heliosearch.org/solrs-new-re-ranking-feature/ > > > On Wed, Jul 23, 2014 at 11:27 AM, Erick Erickson <erickerick...@gmail.com> > 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 the original sort? > > > > At the end, you have your original list in it's original order, with > > (potentially) some > > documents removed that don't satisfy the secondary query. > > > > Or I'm missing the boat entirely. > > > > Best, > > Erick > > > > > > On Wed, Jul 23, 2014 at 6:31 AM, Peter Keegan <peterlkee...@gmail.com> > > wrote: > > > > > I'm looking at how 'ReRankQuery' works. If the main query has a Sort > > > criteria, it is only used to sort the first pass results. The > QueryScorer > > > used in the second pass only reorders the ScoreDocs based on score and > > > docid, but doesn't use the original Sort fields. If the Sort criteria > is > > > 'score desc, myfield asc', I would expect 'myfield' to break score ties > > > from the second pass after rescoring. > > > > > > Is this a bug or the intended behavior? > > > > > > Thanks, > > > Peter > > > > > >
