Hi Thomas, Yes, it may be about time to upgrade from 3.2.0. I think I will have to look into that. Thanks for sharing your insight and configuration example.
Kind regards, Stian søn. 18. sep. 2022 kl. 16:21 skrev Thomas Corthals <tho...@klascement.net>: > Hi Stian, > > We have the same issue with our documents. I fixed that by setting b = 0 in > our schema for BM25 similarity. > > <similarity class="solr.BM25SimilarityFactory"> > <float name="b">0</float> > </similarity> > > I don't know if BM25 can be used with your version of Solr. Personally I > think it's worth upgrading for. > > Thomas > > > Op za 17 sep. 2022 om 19:30 schreef Stian Brattland <st...@octetnest.no>: > > > Hi, > > > > I have a Solr (3.2.0) instance with omitNorms=true on all fields. This > has > > been done in an attempt to not penalize documents which have many terms. > > > > What puzzles me is that, despite omitNorms=true, the fieldNorm is still > > calculated and affects the score. > > > > --- > > 3.7455106 = (MATCH) fieldWeight(track_hierarchynode:pop in 258465), > > product of: > > 2.236068 = tf(termFreq(track_hierarchynode:pop)=5) > > 6.700173 = idf(docFreq=6960, maxDocs=2080776) > > 0.25 = fieldNorm(field=track_hierarchynode, doc=258465) > > --- > > > > How is the fieldNorm value calculated when omitNorms=true? > > > > Kind regards, > > Stian Brattland > > >
