lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe <tomasflo...@gmail.com>
Subject Re: overriding qf in q affecting boosts
Date Mon, 05 Dec 2011 12:17:59 GMT
Hi Robert, the answer depends on the query parser you are using. If you are
using the "edismax" query parser, then the "qf" will only be used when you
don't specify any field in the "q" parameter. In your example the result
query will be, boolean queries for "this" and "that" in the field1 and a
DisMax query for the term "other" in fields (and the boost) you specify in
qf.

If you use "dismax" the field in the query will not be considered and if
you use LuceneQP the qf are not considered and it is going to use the
default search field for the term "other" and no boost.

You can see this very easily turning on the "debugQuery".

Regards,

Tomás

On Mon, Dec 5, 2011 at 8:18 AM, Robert Brown <rob@intelcompute.com> wrote:

> If I have a set list in solrconfig for my "qf" along with their boosts,
> and I then specify field names directly in q (where I could also override
> the boosts), are the boosts left in place, or reset to 1?
>
>
> <str name="qf">
>  this^3
>  that^2
>  other^9
> </str>
>
>
> ie q=field1:+(this that) +(other)
>
>
>
>
>
> --
>
> IntelCompute
> Web Design & Local Online Marketing
>
> http://www.intelcompute.com
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message