[OAK-4906] Lucene: Support relative property based query by transforming the path

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.7.7, 1.8.0
• Component/s: lucene
• Sprint: L10
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 10/Oct/16 06:01
• Updated: 26/Jun/19 12:56
• Resolved: 30/Aug/17 04:06

Description

PropertyIndex supports query like below

/jcr:root//*[jcr:content/@keywords]

For such query keywords property is indexed and the as part of Cursor returned for the query the path is transformed to return the parent path if the parent node is jcr:content

Currently LucenePropertyIndex supports indexing relative properties wrt base node like jcr:content/metadata/status. Here it would index the relative property by refererring to its relative name.

To simplify switch to LucenePropertyIndex (as part of hybrid index support) LucenePropertyIndex should also support for such queries where property index definition only specifies indexing keywords but the query is using a relative property. So LucenePropertyIndex should

1. First check if it has a property definition for jcr:content/keywords
2. If not check if the indexingRule is for nt:base
3. If yes check if it has property definition for keywords
4. If yes then use the index to evaluate the query and return transformed result

LucenePropertyIndex already do such transformations for fulltext constraints. With this we extend that support for property restrictions also

Issue Links

• blocks: OAK-8437 direct children, exact, and parent path restrictions don't work when path transformation takes place
• is related to: OAK-6535 Synchronous Lucene Property Indexes
• relates to: OAK-4412 Lucene hybrid index