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 "Stefan Egli (JIRA)" <ji...@apache.org> on 2016/11/25 09:31:59 UTC

[jira] [Created] (OAK-5164) ChangeSet's maxPathDepth must be taken into account by ChangeSetFilterImpl

Stefan Egli created OAK-5164:
--------------------------------

             Summary: ChangeSet's maxPathDepth must be taken into account by ChangeSetFilterImpl
                 Key: OAK-5164
                 URL: https://issues.apache.org/jira/browse/OAK-5164
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: core
    Affects Versions: 1.5.14
            Reporter: Stefan Egli
            Assignee: Stefan Egli
            Priority: Critical
             Fix For: 1.5.15


The ChangeSet stops collecting paths that are deeper than {{maxPathDepth}}. This is to avoid collecting too much detail (and overflow the ChangeSet) given normally filters' includePaths are only a few levels deep.

This information is currently however not yet used by the ChangeSetFilterImpl. This is wrong and must be fixed. At the moment it's not a realistic problem though as the {{maxPathDepth}} is 9 and typically filters have include paths of perhaps 2-4. But with ChangeSet merging (OAK-5126) that figure of 9 might come down, so accounting for {{maxPathDepth}} in the filter must be done at some point.



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