it.
> >
> > The manual is not clear about this though, any recommendations?
> >
> > Thanks,
> > Markus
> >
> > -Original message-
> > > From:Shalin Shekhar Mangar
> > > Sent: Tuesday 27th September 2016 14:41
> > > To: sol
uesday 27th September 2016 14:41
> > To: solr-user@lucene.apache.org
> > Subject: Re: Results not ordered by score and debug info is incorrect,
> crazy
> >
> > This may be relevant or not, I am not sure but one difference between
> > fl=title_nl,score,id and fl=score,
s, so i didn't enable it.
The manual is not clear about this though, any recommendations?
Thanks,
Markus
-Original message-
> From:Shalin Shekhar Mangar
> Sent: Tuesday 27th September 2016 14:41
> To: solr-user@lucene.apache.org
> Subject: Re: Results not ordered by sco
This may be relevant or not, I am not sure but one difference between
fl=title_nl,score,id and fl=score,id is that the former executes a two pass
distributed search i.e. get ids, merge, get fields for top N docs but the
latter skips the "get fields" phase because it already has all the right
inform
Hi,
I just spotted something weird, again. A regular search popped up a weird
candidate for first result, so i've reproduced it on our production system.
Digging deeper, it appears that the fl parameter has something to do with it.
Not the order of results but the scores / explain in the debug
