Checking it further by looking at the code, it seems that in most cases
it indeed adds the boost queries as SHOULD. But if you define *one* bq
parameter which contains a boolean query, then each clause in this
boolean query will be added to the query as is. Therefore:
This set up will filter t
Well.. this is mainly based on some experiments I did (not based on the
code base). It appeared as if the boost queries were appended to the
generated dismax query and if the default operator (in the schema) was
set to AND it actually filtered out the request. For example, here's a
dismax confi
Are you sure about the default operator and bq? I assume we're
talking about the setting in schema.xml.
I think boosting queries are OR'd in automatically to the main query:
From DismaxQParser#addBoostQuery()
... query.add(f, BooleanClause.Occur.SHOULD);...
There is one case where query.ad
You can actually define boost queries to do that (bq parameter). Boost
queries accept the standard Lucene query syntax and eventually appended
to the user query. Just make sure that the default operator is set to OR
other wise these boost queries will not only influence the boosts but
also filt
Terms no, but fields (with terms) and phrases, yes.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
> From: Girish Redekar
> To: solr-user@lucene.apache.org
> Sent: Fri, December 4, 2009 11:42:16 PM
> Subject: Query time boosting with dismax
>
>
