[
https://issues.apache.org/jira/browse/OAK-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh resolved OAK-8271.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.16.0
Applied [^OAK-8271.patch] on trunk at
[r1861270|https://svn.apache.org/r1861270]. Added a bit of clarification in doc
for dynamic operand for xpath and sql2 at
[r1861271|https://svn.apache.org/r1861271].
> Lucene path transformed result doesn't accomodate wildcards in relative path
> ----------------------------------------------------------------------------
>
> Key: OAK-8271
> URL: https://issues.apache.org/jira/browse/OAK-8271
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.16.0
>
> Attachments: OAK-8271.patch
>
>
> {{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
> {noformat}
> + /oak:index/fooIndex/indexRules/nt:base/properties
> + foo
> - propertyIndex=true
> {noformat}
> we can answer queries such as
> {noformat}
> /jcr:root/a//element(*, some:type)[b/foo='bar']
> /jcr:root/a//element(*, some:type)[b/c/foo='bar']
> {noformat}
> In the same spirit it could also support query with wildcard in relative path
> fragment
> {noformat}
> /jcr:root/a//element(*, some:type)[b/*/foo='bar']
> {noformat}
> .... but it doesn't work currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
