[OAK-6217] Document tricky statements

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.10.0
• Component/s: query
• Epic Link: indexer resilience
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 12/May/17 09:51
• Updated: 16/Jan/19 11:41
• Resolved: 26/Jan/18 11:16

Description

There are some cases, specially if fulltext conditions and aggregation are used, where a query sometimes returns no results even thought with the right index it does return the results. This is a bit hard to understand, because it doesn't match the rule "indexes should only affect performance, not results". One such example is if a query uses one or the other index, but not both. Or if a query uses fulltext conditions on different nodes (parent and child). Examples:

/jcr:root/home//element(*, rep:User)
  [jcr:contains(.,'Kerr*') 
  and jcr:like(@rep:impersonators, '%ccibu%')]/profile
/jcr:root/home//element(*, rep:User)
  [jcr:contains(profile,'Kerr*') 
  and jcr:like(@rep:impersonators, '%ccibu%')]/profile

Related is the usage of relative properties in indexes, excluded / included paths.

Issue Links

• is related to: OAK-5473 Document fulltext search grammer ("contains")
• is related to: OAK-5520 Improve index and query documentation
• relates to: OAK-6898 Query: grammar documentation / annotated railroad diagrams