Paste your Solr query into here http://splainer.io and it will help you
debug your scoring/matching (shameless plug I made this thing)

Also I suspect you may be using edismax. In which case the
inclusion/exclusion of explicit ORs might turn a query from a big OR query
into possibly a dismax query which maybe changes the structure of the query?

On Wed, Jan 13, 2016 at 10:05 AM, Emir Arnautovic <
emir.arnauto...@sematext.com> wrote:

> Hi Sara,
> You can run your query (or smaller one) with debugQuery=true and see how
> it is rewritten.
>
> Thanks,
> Emir
>
>
> On 13.01.2016 16:01, sara hajili wrote:
>
>> tnx.
>> and my main question is about maxBooleanDefault in solr config.
>> it is 1024 by default.
>> and i have a edismax query with about 500 words in this way:
>> q1= str1 OR str2 OR str3 ...OR strn
>> it throws exception that cant't parse query too boolean clause.
>> so if i changed maxBooleanDefault to 1500 it works
>> but some thing is ambiguous for me is when i don;t change
>> maxBooleanDefault
>> and it remains 1024.
>> but i changed query in this way
>> q2 = str1 str2 str3 ... strn // i eliminated OR between for and inside
>> space
>> i didn't get exception !!!
>> why?!
>> what is diffrence between q1 an q2??
>>
>> On Wed, Jan 13, 2016 at 6:28 AM, Shawn Heisey <apa...@elyograg.org>
>> wrote:
>>
>> On 1/13/2016 5:40 AM, sara hajili wrote:
>>>
>>>> what is exactly diffrence between sapce and OR in solr query  ?
>>>> i mean what is diffrence  between
>>>> q = solr OR lucene OR search
>>>> and this
>>>> q = solr lucene search?
>>>>
>>>> solr default boolean occurence is OR,isn't it?
>>>>
>>> This depends on what the default operator is.  The default for the
>>> default operator is OR, and that would produce exactly the same results
>>> for both of the queries you have mentioned.  If the default operator is
>>> AND, then those two queries would be different.
>>>
>>> The default operator applies to the lucene and edismax parsers.  The
>>> lucene parser is Solr's default.  In older versions, the default
>>> operator could be set by a defaultOperator parameter.  I do not remember
>>> whether that was in solrconfig or schema.  That parameter is deprecated
>>> and the q.op parameter should be used now.
>>>
>>> Thanks,
>>> Shawn
>>>
>>>
>>>
> --
> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
> Solr & Elasticsearch Support * http://sematext.com/
>
>


-- 
*Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections
<http://opensourceconnections.com>, LLC | 240.476.9983
Author: Relevant Search <http://manning.com/turnbull>
This e-mail and all contents, including attachments, is considered to be
Company Confidential unless explicitly stated otherwise, regardless
of whether attachments are marked as such.

Reply via email to