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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/05/02 17:16:16 UTC

[jira] [Commented] (OAK-806) Content migration from Jackrabbit to Oak

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

Jukka Zitting commented on OAK-806:
-----------------------------------

Initial, far from complete draft committed in http://svn.apache.org/r1478405. 
                
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira