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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2015/08/04 16:19:04 UTC
[jira] [Updated] (OAK-2586) Support including and excluding paths
during upgrade
[ https://issues.apache.org/jira/browse/OAK-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomek Rękawek updated OAK-2586:
-------------------------------
Attachment: OAK-2586-August.patch
I attached the patch version aligned to the current trunk. Patch is created from the [issue branch|https://github.com/trekawek/jackrabbit-oak/tree/OAK-2586] on my github.
> 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-August.patch, 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)