[
https://issues.apache.org/jira/browse/OAK-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352709#comment-14352709
]
Chetan Mehrotra commented on OAK-2586:
--------------------------------------
This looks useful! What I am not sure is would wrapping of {{NodeState}} would
lead to unoptimized code path particularly in equals evaluation where the
specific NodeState implementation do take a faster approach if instance passed
is of same type. May be the equals can "unwrap" the NodeState and then perform
equals.
[~mduerig] Thoughts?
> 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
(v6.3.4#6332)
