Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-6217

Document tricky statements

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.10.0
    • Component/s: query
    • Labels:
      None

      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.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              thomasm Thomas Mueller
              Reporter:
              thomasm Thomas Mueller

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment