Thanks a lot Jack, it makes total sense. I check the config and default q.op
was set to OR, which was influencing the query.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Boost-Query-bq-syntax-usage-tp4161989p4162169.html
Sent from the Solr - User mailing list archive at N
dismax and then specify edismax for bq using the localParam notation.
-- Jack Krupansky
-Original Message-
From: Jack Krupansky
Sent: Tuesday, September 30, 2014 8:19 PM
To: solr-user@lucene.apache.org
Subject: Re: Boost Query (bq) syntax/usage
The "+" signs in the parsed b
solr-user@lucene.apache.org
Subject: Re: Boost Query (bq) syntax/usage
Thanks a lot Jack, makes sense. Just curios, if we used the following bq
entry in solrconfig xml
Source2:sfdc^6 Source2:downloads^5 Source2:topics^3
will it always be treated as an AND query ? Some of local results suggests
Thanks a lot Jack, makes sense. Just curios, if we used the following bq
entry in solrconfig xml
Source2:sfdc^6 Source2:downloads^5 Source2:topics^3
will it always be treated as an AND query ? Some of local results suggests
otherwise.
--
View this message in context:
http://lucene.472066.n3
A boost is basically an "OR" operation - it doesn't select any more or fewer
documents. So, three separate bq's are three OR terms. But your first bq is
a single query that ANDs three terms, and that AND-ed query is OR-ed with
the original query, so it only boosts documents that contain all thre
