[
https://issues.apache.org/jira/browse/SOLR-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509590#comment-13509590
]
Leonhard Maylein commented on SOLR-4141:
----------------------------------------
Oh, what a pity!
Then I have to check to user query in the front end first to
decide if the edismax parser is applicable or not.
If the user types in parentheses, there is no chance to use the
edismax handler because the user would be very surprised by
the the result.
Or, perhaps, I have to prefix every word within the parentheses
with a plus sign (and if there are camel case words I have to
separate the word parts before). But I think this is not the
whole purpose of the edismax query parser.
> EDismax: Strange combination of subqueries with parentheses
> -----------------------------------------------------------
>
> Key: SOLR-4141
> URL: https://issues.apache.org/jira/browse/SOLR-4141
> Project: Solr
> Issue Type: Bug
> Components: query parsers
> Affects Versions: 4.0
> Reporter: Leonhard Maylein
>
> fi = field name, mm=100% (all examples)
> The query 'fi:a fi:b'
> (parsed query: '(+((fi:a fi:b)~2))/no_coord')
> is interpreted as 'fi:a AND fi:b'
> This also applies to the queries '(fi:a fi:b)' respectively
> 'fi:(a b)'.
> But the query '(fi:a fi:b) (fi:a fi:b)'
> (parsed query: '(+(((fi:a fi:b) (fi:a fi:b))~2))/no_coord')
> shows the same result as 'fi:a OR fi:b'.
> I'm not sure but I think this is a bug, isn't it?
> If it's a intended behavior I think it is very difficult
> to explain this to a searcher.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
