You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Mark Fletcher <ma...@gmail.com> on 2010/04/06 01:31:21 UTC

exact match coming as second record

Hi,

I am using the dismax handler.
I have a field named *myfield* which has a value say XXX.YYY.ZZZ. I have
boosted myfield^20.0.
Even with such a high boost (in fact among the qf fields specified this
field has the max boost given), when I search for XXX.YYY.ZZZ I see my
record as the second one in the results and a record of  the form
XXX.YYY.ZZZ.AAA.BBB is appearing as the first one.

Can any one help me understand why is this so, as I thought an exact match
on a heavily boosted field would give the exact match record first in
dismax.

Thanks and Rgds,
Mark

Re: exact match coming as second record

Posted by Mark Fletcher <ma...@gmail.com>.
Hi Eric,

Thanks many for your mail!
Please find attached the debugQuery results.

Thanks!
Mark

On Mon, Apr 5, 2010 at 7:38 PM, Erick Erickson <er...@gmail.com>wrote:

> What do you get back when you specify &debugQuery=on?
>
> Best
> Erick
>
> On Mon, Apr 5, 2010 at 7:31 PM, Mark Fletcher
> <ma...@gmail.com>wrote:
>
>  > Hi,
> >
> > I am using the dismax handler.
> > I have a field named *myfield* which has a value say XXX.YYY.ZZZ. I have
> > boosted myfield^20.0.
> > Even with such a high boost (in fact among the qf fields specified this
> > field has the max boost given), when I search for XXX.YYY.ZZZ I see my
> > record as the second one in the results and a record of  the form
> > XXX.YYY.ZZZ.AAA.BBB is appearing as the first one.
> >
> > Can any one help me understand why is this so, as I thought an exact
> match
> > on a heavily boosted field would give the exact match record first in
> > dismax.
> >
> > Thanks and Rgds,
> > Mark
> >
>

Re: exact match coming as second record

Posted by Erick Erickson <er...@gmail.com>.
What do you get back when you specify &debugQuery=on?

Best
Erick

On Mon, Apr 5, 2010 at 7:31 PM, Mark Fletcher
<ma...@gmail.com>wrote:

> Hi,
>
> I am using the dismax handler.
> I have a field named *myfield* which has a value say XXX.YYY.ZZZ. I have
> boosted myfield^20.0.
> Even with such a high boost (in fact among the qf fields specified this
> field has the max boost given), when I search for XXX.YYY.ZZZ I see my
> record as the second one in the results and a record of  the form
> XXX.YYY.ZZZ.AAA.BBB is appearing as the first one.
>
> Can any one help me understand why is this so, as I thought an exact match
> on a heavily boosted field would give the exact match record first in
> dismax.
>
> Thanks and Rgds,
> Mark
>