lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-7483) QueryParser changes OR clausule to AND
Date Fri, 07 Oct 2016 17:35:20 GMT

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

Hoss Man commented on LUCENE-7483:
----------------------------------

Yep ... it's the consequence of using the "boolean" operators instead of the unary operators
... 

https://lucidworks.com/blog/2011/12/28/why-not-and-or-and-not/

> QueryParser changes OR clausule to AND
> --------------------------------------
>
>                 Key: LUCENE-7483
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7483
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/queryparser
>    Affects Versions: 6.2.1
>            Reporter: Júlio César e Melo
>            Priority: Minor
>
> QueryParser incorrectly parses the expression {color:blue}{{t1 AND t2 *OR* t3 AND t4}}{color}
as
> {color:red}{{(+t1 +t2 +t3 +t4)}}{color} while {color:green}{{t1 AND t2 AND t3 AND t4}}{color}
produces the same result.
> The expected result for expression {color:blue}{{t1 AND t2 OR t3 AND t4}}{color} is {color:purple}{{(+t1
+t2) (+t3 +t4)}}{color}.
> This occurs using StandardQueryParser or classic.QueryParser.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message