Personally I was expecting the sort request parameter to be applied on the
final search results:
1) run original query, get top K based on score
2) run re rank query on the top K, recalculate the scores
3) finally apply the sort
But when you mentioned "you expect the sort specified to be applied t
OK so to restate, you expect the sort specified to be applied to both the
“outer” and “inner” queries. Makes sense, seems like a good enhancement.
Hmm, I wonder if you can put the sort parameter in with the rerank
specification, like: q={!rerank reRankQuery=$rqq reRankDocs=1200 reRankWeight=3
s
In the first OK scenario, the search results are sorted with score desc,
and when the score is identical, the secondary sort field is applied.
In the KO scenario, only score desc is taken into consideration(the
reranked score) , the secondary sort by the sort field is ignored.
I suspect an intuit
Hmmm, can we see a bit of sample output? I always have to read this backwards,
the outer query results are sent to the inner query, so my _guess_ is that the
sort is applied to the “q=*:*” and then the top 1,200 are sorted by score by
the rerank. But then I’m often confused about this.
Erick
>
Hi all,
I was playing a bit with the reranking capability and I discovered that:
*Sort by score, then by secondary field -> OK*
http://localhost:8983/solr/books/select?q=vegeta ssj&*sort=score
desc,downloads desc*&fl=id,title,score,downloads
*ReRank, Sort by score, then by secondary field -> KO*
