[OAK-955] Query: Filter doesn't contain fulltext constraints from joins

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Fix Version/s: 1.3.7, 1.4
• Component/s: core, query
• Labels: performance resilience
• Epic Link: Query performance improvements
• Assignee: Thomas Mueller
• Reporter: Alex Deparvu
• Created: 12/Aug/13 08:49
• Updated: 02/Mar/16 15:34
• Resolved: 10/Sep/15 14:26

Description

Example query:

SELECT a.* 
FROM [nt:unstructured] AS a 
INNER JOIN [nt:unstructured] AS b 
ON b.[jcr:uuid] = a.testref 
WHERE a.type = 'child' 
AND (CONTAINS(a.*, 'testJoinWithOR4') OR b.type = 'parent' AND CONTAINS(b.*, 'testJoinWithOR4'))

I'm not sure why this happens, but I noticed stepping through the code that the filter generated on the query doesn't contain any fulltext constraints. It does however contain the 'type' info which will trick the query engine into picking a property index, failing the test because is returns more results than it should.

See failing tests on the lucene module:

• org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR4
• org.apache.jackrabbit.core.query.JoinTest#testJoinWithOR5

Issue Links

• is blocked by: OAK-1617 Automatically convert "or" queries to "union" for SQL-2
• is related to: OAK-957 SQL2NodeLocalNameTest test failures