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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2016/12/22 14:09:58 UTC

[jira] [Resolved] (OAK-5366) Optimize pre-filtering with long paths

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

Marcel Reutegger resolved OAK-5366.
-----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.8)
                   1.6
                   1.5.17

Implemented in trunk: http://svn.apache.org/r1775660

> Optimize pre-filtering with long paths
> --------------------------------------
>
>                 Key: OAK-5366
>                 URL: https://issues.apache.org/jira/browse/OAK-5366
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.5.17, 1.6
>
>
> ChangeSetFilterImpl.doExcludes(ChangeSet) currently returns quickly with {{false}} when the ChangeSet reached maxPathDepth. The default maxPathDepth is 9 and some applications may hit this limit quite frequently. E.g. Apache Sling's job implementation stores frequently modified job data further down the hierarchy.
> A quick win in this case might be to at least check the first level path include names.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)