[
https://issues.apache.org/jira/browse/OAK-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-6217:
--------------------------------
Fix Version/s: (was: 1.8)
1.9
> Document tricky statements
> --------------------------
>
> Key: OAK-6217
> URL: https://issues.apache.org/jira/browse/OAK-6217
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 1.9
>
>
> 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:
> {noformat}
> /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
> {noformat}
> Related is the usage of relative properties in indexes, excluded / included
> paths.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
