[OAK-2660] Wrong result when using multiple OR conditions, with a Lucene full-text index

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.7
• Fix Version/s: 1.3.9, 1.4
• Component/s: query
• Assignee: Davide Giannella
• Reporter: Davide Giannella
• Created: 20/Mar/15 17:24
• Updated: 02/Mar/16 14:47
• Resolved: 22/Oct/15 08:01

Description

The following query returns the wrong result:

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 

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.

Issue Links

• relates to: OAK-2539 SQL2 query not working with filter (s.[stringa] = 'a' OR CONTAINS(s.[stringb], 'b'))
• relates to: OAK-1617 Automatically convert "or" queries to "union" for SQL-2