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 "Andrei Dulceanu (Jira)" <ji...@apache.org> on 2021/01/21 12:42:10 UTC

[jira] [Updated] (OAK-5897) Optimize like constraint support in Property Indexes

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

Andrei Dulceanu updated OAK-5897:
---------------------------------
    Fix Version/s:     (was: 1.38.0)
                   1.40.0

> Optimize like constraint support in Property Indexes
> ----------------------------------------------------
>
>                 Key: OAK-5897
>                 URL: https://issues.apache.org/jira/browse/OAK-5897
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: property-index
>            Reporter: Chetan Mehrotra
>            Assignee: Thomas Mueller
>            Priority: Major
>             Fix For: 1.40.0
>
>
> Consider a query
> {noformat}
>  /jcr:root/content//element(*, nt:unstructured)[jcr:like(@resource, '/content/foo/bar%')]
> {noformat}
> This currently gets translated into a range property restriction 
> {noformat}
>  property=[resource=[[/content/foo/bar.., ../content/foo/bas]]]
> {noformat}
> For such a query property index currently returns all nodes having "resource" property i.e. all index data. This can be optimized to return only those nodes where indexed value qualifies the range property restriction



--
This message was sent by Atlassian Jira
(v8.3.4#803005)