You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/11/30 05:08:58 UTC

[jira] [Updated] (OAK-5187) Support regex for relative property path while indexing properties

     [ https://issues.apache.org/jira/browse/OAK-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra updated OAK-5187:
---------------------------------
    Description: 
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'

  was:
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'


> 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)