a) Need to know in AEM 6.x how an SQL2 query with path constraints works , does this filters first by property data = 'english' say (1) and then iterate each result in (1) to filter the path constraint
SELECT * FROM [nt:base] AS s ISDESCENDANTNODE( s,'/content/sample/') AND CONTAINS(s.data, 'english')
b) What will be the effect of having a oak lucene index with evaluatePathRestrictions and how does that improve the above query
c) Also want to know if the same query is run on AEM 5.6.1 will it have the same performance or will path constraint reduce the performance ? if so why
Overall want to understand does oak lucene indexes support path based indexes or just path level filters over property / node type lucene indexes
