[
https://issues.apache.org/jira/browse/OAK-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Marth updated OAK-806:
------------------------------
Fix Version/s: 0.11
> Content migration from Jackrabbit to Oak
> ----------------------------------------
>
> Key: OAK-806
> URL: https://issues.apache.org/jira/browse/OAK-806
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, jcr, mk
> Reporter: Jukka Zitting
> Fix For: 0.11
>
>
> There should be a mechanism, similar to the backup/migration tool in
> jackrabbit-standalone, that allows us to migrate content from existing
> Jackrabbit repositories to Oak.
> Content should get migrated as-is with as few changes to the content
> structure as possible (ideally none). Extra Oak content like pre-compiled
> type and ACL infromation and search indexes should be added on top of
> existing content, ideally by using the normal commit hooks to process the
> entire migrated set of content.
> It would also be useful if the migration could avoid copying large binaries
> from an existing DataStore that the target MK can access (see OAK-805).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
