lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Walter Underwood <wun...@wunderwood.org>
Subject Re: Solr relevancy score different on replicated nodes
Date Tue, 29 Jan 2019 18:47:35 GMT
Is this a sharded Solr Cloud collection? If so, you can try using global IDF.
That should make the scores more similar on different nodes.

https://lucene.apache.org/solr/guide/6_6/distributed-requests.html#DistributedRequests-ConfiguringstatsCache_DistributedIDF_

wunder
Walter Underwood
wunder@wunderwood.org
http://observer.wunderwood.org/  (my blog)

> On Jan 29, 2019, at 10:38 AM, David Hastings <hastings.recursive@gmail.com> wrote:
> 
> Maybe instead of using the solr score in your metrics, find a way to use
> the documents location in the results?   you can never trust the score to
> be consistent, its constantly changing as the indexes changes
> 
> On Tue, Jan 29, 2019 at 1:29 PM Ashish Bisht <bishtashish77@gmail.com>
> wrote:
> 
>> Hi Erick,
>> 
>> Our business wanted score not to be totally based on default relevancy
>> algo.
>> Instead a mix of solr relevancy+usermetrics(80%+20%).
>> 
>> Each result doc is calculated against max score as a fraction of
>> 80.Remaining 20 is from user metrics.
>> 
>> Finally sort happens on new score.
>> 
>> But say we got first page correctly, and for the second page if the request
>> goes to other replica where max score is different. UI may result give
>> wrong
>> sort as compared to first page. For e.g last value of page 1 is 70 and
>> first
>> value of second page can be 72 I. e distorted sorting.
>> 
>> On top of it we are not using pagination but a infinite scroll which makes
>> it more noticeable.
>> 
>> Please suggest.
>> 
>> Regards
>> Ashish
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> --
>> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
>> 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message