[ 
https://issues.apache.org/jira/browse/SOLR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471685#comment-13471685
 ] 

Shawn Heisey commented on SOLR-3377:
------------------------------------

I have come across something similar to this in Solr 3.5.0.  I am wondering if 
this problem is fixed by this issue in the upcoming 4.0.  I don't have a 4.0 
index at the moment that I can test on.

query:
{code}((feature:depphotos) OR (feature:glowimages) OR (feature:ipurestockx)  
(Kitchen))
{code}

handler definition:
{code}
    <str name="defType">edismax</str>
    <str name="echoParams">all</str>
    <int name="rows">70</int>
    <str 
name="shards">idxa2.REDACTED.com:8981/solr/inclive,idxa1.REDACTED.com:8981/solr/s0live,idxa1.REDACTED.com:8981/solr/s1live,idxa1.REDACTED.com:8981/solr/s2live,idxa2.REDACTED.com:8981/solr/s3live,idxa2.REDACTED.com:8981/solr/s4live,idxa2.REDACTED.com:8981/solr/s5live</str>
    <float name="tie">0.1</float>
    <int name="qs">3</int>
    <int name="ps">3</int>
    <str name="qf">catchall</str>
    <str name="pf">catchall^2</str>
    <str name="boost">
      recip(ms(NOW/DAY,pd),3.16e-11,1,1)
    </str>
    <str name="fl">score,*</str>
    <str name="mm">100%</str>
    <str name="q.alt">*:*</str>
    <bool name="lowercaseOperators">false</bool>
{code}

parsedquery_toString:
{code}
boost(+(feature:depphotos feature:glowimages feature:ipurestockx 
(catchall:kitchen)~0.1) (catchall:"(feature:depphotos feature) depphotos 
(feature:glowimages feature) glowimages (feature:ipurestockx feature) 
ipurestockx 
kitchen"~3^2.0)~0.1,1.0/(3.16E-11*float(ms(const(1349654400000),date(pd)))+1.0))
{code}

Adding some spaces fixes it:
{code}(( feature:depphotos ) OR ( feature:glowimages ) OR ( feature:ipurestockx 
)  (Kitchen))
{code}

becomes:

{code}boost(+(feature:depphotos feature:glowimages feature:ipurestockx 
(catchall:kitchen)~0.1) 
(),1.0/(3.16E-11*float(ms(const(1349654400000),date(pd)))+1.0))
{code}

It also suffers from the problem where the default operator (AND in our case) 
is ignored, but I believe that issue is already filed.

                
> eDismax: A fielded query wrapped by parens is not recognized
> ------------------------------------------------------------
>
>                 Key: SOLR-3377
>                 URL: https://issues.apache.org/jira/browse/SOLR-3377
>             Project: Solr
>          Issue Type: Bug
>          Components: query parsers
>    Affects Versions: 3.6
>            Reporter: Jan Høydahl
>            Assignee: Yonik Seeley
>            Priority: Critical
>             Fix For: 4.0-BETA
>
>         Attachments: SOLR-3377.patch, SOLR-3377.patch, SOLR-3377.patch, 
> SOLR-3377.patch
>
>
> As reported by "bernd" on the user list, a query like this
> {{q=(name:test)}}
> will yield 0 hits in 3.6 while it worked in 3.5. It works without the parens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to