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

Lucene path transformed result doesn't accomodate wildcards in relative path

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.10.3, 1.8.14, 1.16.0
    • Component/s: lucene
    • Labels:
      None

      Description

      LucenePropertyIndex support answering a query with property constraint on a relative path if there's an property (non-relative) is indexed on nt:base.
      e.g. with an index def such as

      + /oak:index/fooIndex/indexRules/nt:base/properties
         + foo
             - propertyIndex=true
      

      we can answer queries such as

      /jcr:root/a//element(*, some:type)[b/foo='bar']
      /jcr:root/a//element(*, some:type)[b/c/foo='bar']
      

      In the same spirit it could also support query with wildcard in relative path fragment

      /jcr:root/a//element(*, some:type)[b/*/foo='bar']
      

      .... but it doesn't work currently.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              catholicon Vikas Saurabh
              Reporter:
              catholicon Vikas Saurabh

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment