[
https://issues.apache.org/jira/browse/OAK-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957063#comment-14957063
]
Davide Giannella commented on OAK-2660:
---------------------------------------
This will be fixed with the latest implementation of OAK-1617:
[OAK-1617-3.patch|https://issues.apache.org/jira/secure/attachment/12766561/OAK-1617-3.patch].
The Query and Query Engine contain the logic to understand special use
cases and opt for optimisations in case.
> Wrong result when using multiple OR conditions, with a Lucene full-text index
> -----------------------------------------------------------------------------
>
> Key: OAK-2660
> URL: https://issues.apache.org/jira/browse/OAK-2660
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Affects Versions: 1.1.7
> Reporter: Davide Giannella
> Assignee: Davide Giannella
> Fix For: 1.4
>
>
> The following query returns the wrong result:
> {code}
> SELECT *
> FROM [nt:unstructured] AS c
> WHERE ( c.[name] = 'yes'
> OR CONTAINS(c.[surname], 'yes')
> OR CONTAINS(c.[description], 'yes') )
> AND ISDESCENDANTNODE(c, '/content')
> ORDER BY added DESC
> {code}
> There is a Lucene property index for the following properties: {{name,
> surname, description, added}}.
> Internally, the FilterImpl passed to the indexes does not contains any
> conditions except order and path restriction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
