jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Sedding (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2586) Support including and excluding paths during upgrade
Date Mon, 09 Mar 2015 10:36:39 GMT

    [ https://issues.apache.org/jira/browse/OAK-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352769#comment-14352769

Julian Sedding commented on OAK-2586:

Thanks for the feedback [~chetanm] and [~mduerig]. I agree that we need to make sure that
performance does not suffer from this and we should measure performance to avoid any degradation.

I have tried to address any performance concerns by only wrapping NodeState that need to be
wrapped (i.e. only NodeStates that are themselves hidden or have hidden descendants). Thus
for the default case without any includes/excludes, no wrapping should occur at all.

I'll see if I can come up with a way to measure performance. Ideas welcome!

> Support including and excluding paths during upgrade
> ----------------------------------------------------
>                 Key: OAK-2586
>                 URL: https://issues.apache.org/jira/browse/OAK-2586
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: upgrade
>    Affects Versions: 1.1.6
>            Reporter: Julian Sedding
>              Labels: patch
>         Attachments: OAK-2586.patch
> When upgrading a Jackrabbit 2 to an Oak repository it can be desirable to constrain which
paths/sub-trees should be copied from the source repository. Not least because this can (drastically)
reduce the amount of content that needs to be traversed, copied and indexed.
> I suggest to allow filtering the content visible from the source repository by wrapping
the JackrabbitNodeState instance and hiding selected paths.

This message was sent by Atlassian JIRA

View raw message