[OAK-8271] Lucene path transformed result doesn't accomodate wildcards in relative path

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.10.3, 1.8.14, 1.16.0
• Component/s: lucene
• Assignee: Vikas Saurabh
• Reporter: Vikas Saurabh
• Created: 24/Apr/19 10:55
• Updated: 08/Oct/19 15:22
• Resolved: 13/Jun/19 15:40

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.

Issue Links

• is required by: OAK-8437 direct children, exact, and parent path restrictions don't work when path transformation takes place