[
https://issues.apache.org/jira/browse/OAK-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella resolved OAK-2660.
-----------------------------------
Resolution: Fixed
Consider this resolved as with OAK-1617 enabled the test pass successfully.
https://github.com/apache/jackrabbit-oak/blob/512c8bad4064f5bd392ee530990107f292bcac95/oak-lucene/src/test/java/org/apache/jackrabbit/oak/plugins/index/lucene/LuceneIndexQueryTestSQL2Optimisation.java
> 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.3.9
>
>
> 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)
