[ https://issues.apache.org/jira/browse/OAK-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726909#comment-15726909
]
Thomas März commented on OAK-5187:
----------------------------------
When using globs, please also support {{jcr:content/**/foo}}, since keeping index definitions
up to date with changes in content structure is annoying.
> Support regex for relative property path while indexing properties
> ------------------------------------------------------------------
>
> Key: OAK-5187
> URL: https://issues.apache.org/jira/browse/OAK-5187
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.8
>
>
> Lucene index definition currently support index properties based on regex. The regex
support is currently restricted to property name only and not for relative property paths.
> However at time we have queries like below
> {noformat}
> /jcr:root/content/docs//element(*,app:Asset)[(jcr:content/targeting_123/section_456/@foo=110)]
> {noformat}
> Here the relative property path can vary. To index them we need to support relative property
based on regex or globs 'jcr:content/\*/\*/foo'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|