Re: SOLR Score Range Changed

2018-02-26 Thread Shawn Heisey
On 2/23/2018 2:28 PM, Hodder, Rick wrote: > Combining everything into one query is what I'd prefer because as you said, > one would think that with everything in the same query, the score would > organize everything nicely. I don't recall writing anything like that.  How did you infer that from

RE: SOLR Score Range Changed

2018-02-23 Thread Hodder, Rick
riday, February 23, 2018 10:41 AM To: solr-user@lucene.apache.org Subject: Re: SOLR Score Range Changed The difference seems due to the fact that default similarity in solr 7 is BM25 while it used to be TF-IDF in solr 4. As you realised, BM25 function is smoother. You can configure schema.xml t

RE: SOLR Score Range Changed

2018-02-23 Thread Hodder, Rick
Hi Shawn, Thanks for your help - I'm still finding my way in the weeds of SOLR. Combining everything into one query is what I'd prefer because as you said, one would think that with everything in the same query, the score would organize everything nicely. >>Assuming you're using the default re

Re: SOLR Score Range Changed

2018-02-23 Thread Joël Trigalo
The difference seems due to the fact that default similarity in solr 7 is BM25 while it used to be TF-IDF in solr 4. As you realised, BM25 function is smoother. You can configure schema.xml to use ClassicSimilarity, for instance https://lucene.apache.org/solr/guide/6_6/major-changes-from-solr-5-to-

Re: SOLR Score Range Changed

2018-02-22 Thread Shawn Heisey
On 2/22/2018 9:50 AM, Hodder, Rick wrote: I am migrating from SOLR 4.10.2 to SOLR 7.1. All seems to be going well, except for one thing: the score that is coming back for the resulting documents is giving different scores. The absolute score has no meaning when you change something -- the in