[
https://issues.apache.org/jira/browse/SOLR-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529864#comment-13529864
]
Leonhard Maylein commented on SOLR-4141:
----------------------------------------
In combination with the WordDelimiterFilter setting of mm to 100%
is worthless even if you do not have explicit sub-queries because
of the implicit sub-queries for search terms splitted up by the
WordDelimiterFilter (camel case words, words with hyphens or
letters followed by a digit).
I have changed the Type of this issue from bug to improvement.
> EDismax: Strange combination of subqueries with parentheses
> -----------------------------------------------------------
>
> Key: SOLR-4141
> URL: https://issues.apache.org/jira/browse/SOLR-4141
> Project: Solr
> Issue Type: Improvement
> 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
