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

Jan Høydahl commented on SOLR-3377:
-----------------------------------

Bernd, I agree that this is a bug that absolutely should be fixed.

I have followed it through this far but have not yet had the chance to go the 
last mile until committing, but I am definitely keen to pick it up again after 
summer holidays and parental leave, hopefully before. The reason I unassigned 
myself is to signal to the other committers that I'm not actively working on 
this and let others step in if they wish.

This is the way Apache works - we are all volunteers, and I am sure that with 
some patience this will make it through in time for 4.0 final. You've done a 
great job so far with the patch. It may be "final" and good to go, but 
personally I'd write some more tests since this particular area has been 
lacking - before committing.
                
> 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
>             Fix For: 4.0, 3.6.1
>
>         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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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