It seems like the debug information is using the custom similarity as it should - the bug isn't there. I see in the explain information the right tf value (I modified it to be 1 in my custom similarity). The numbers in the explain seem to add up and make sense. Is it possible that the score itself is wrong (the one that I get from fl)?
Thanks, Yuri On Wed, Aug 27, 2008 at 11:44 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote: > On Wed, Aug 27, 2008 at 9:38 AM, Yuri Jan <[EMAIL PROTECTED]> wrote: > > Actually, no... > > The score in the fl are 12.806475 and 10.386531 respectively, so the > results > > according to that are sorted correctly. > > Is it just a problem with the debugQuery? > > Looks like it... I guess the custom similarity isn't being used when > explain() is called. > Did you register this custom similarity in the schema? > If so, can you file a JIRA bug for this? > > -Yonik > > > > On Wed, Aug 27, 2008 at 9:21 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote: > > > >> On Wed, Aug 27, 2008 at 9:10 AM, Yuri Jan <[EMAIL PROTECTED]> wrote: > >> > I have encountered a weird problem in solr. > >> > In one of my queries (dismax, default sorting) I noticed that the > results > >> > are not sorted by score (according to debugQuery). > >> > > >> > The first 150 results are tied (with score 12.806474), and after > those, > >> > there is a bunch of results with higher score (12.962835). > >> > > >> > What can be the cause? > >> > I'm overriding the tf function in my similarity class. Can it be > related? > >> > >> Do the explain scores in the debug section match the normal scores > >> paired with the documents? (add score to the fl parameter to get a > >> score with each document). > >> > >> -Yonik > >> > > >
