gt; you stopped using that?
>>>
>>> Cheers,
>>>
>>> Tim
>>>
>>> -Original Message-
>>> From: Modassar Ather [mailto:modather1...@gmail.com]
>>> Sent: Monday, November 30, 2015 5:46 AM
>>> To: solr-user@luce
The mm parameter or default operator logic only applies to the top level of
the query. Once you get nested in parentheses below the top level,
Solr/Lucene reverts to the default of the OR (SHOULD) operator.
-- Jack Krupansky
On Mon, Nov 30, 2015 at 5:45 AM, Modassar Ather
wrote:
> Hi,
>
> I hav
On 30 November 2015 at 05:45, Modassar Ather wrote:
>
> I have a query title:(solr lucene api). The mm is set to 100% using q.op as
> +(title:solr **title:faceting** title:api)~3
Does it though? solr lucene api => solr faceting api!
Is it possible you are staring at the wrong tab and the counts
I cannot immediately explain the behaviour you are seeing, but can't you
use a filter query to achieve the same?
Add fq=topic:facet to your query string, and you'll be set.
As to the original behaviour, the parsed query looks wrong, as it is
missing a bracket. Can you provide all of the versions
Hi,
I have a query title:(solr lucene api). The mm is set to 100% using q.op as
AND.
When the query is executed it returns documnets having all the terms. It
parses to following:
+(title:solr title:faceting title:api)~3
Similarlly I have another query like this topic:facet AND title:(solr
lucene
