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 "Manfred Baedke (JIRA)" <ji...@apache.org> on 2015/03/11 19:55:38 UTC

[jira] [Comment Edited] (OAK-1859) Migration from TarMK to MongoMK

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

Manfred Baedke edited comment on OAK-1859 at 3/11/15 6:55 PM:
--------------------------------------------------------------

Implemented in branch 1.0 with revision 1665962 and in trunk with revision 1665964.
The new class RepositorySidegrade works analogously to RepositoryUpgrade.


was (Author: baedke):
Implemented in branch 1.0 with revision 1665962.

> Migration from TarMK to MongoMK
> -------------------------------
>
>                 Key: OAK-1859
>                 URL: https://issues.apache.org/jira/browse/OAK-1859
>             Project: Jackrabbit Oak
>          Issue Type: Wish
>          Components: upgrade
>    Affects Versions: 1.0
>            Reporter: Przemo Pakulski
>            Assignee: Manfred Baedke
>             Fix For: 1.2
>
>
> Is migration from TarMK to MongoMK possible ?
> Let's say I initially used TarMK, then realized that Mongo is better option, is there any way to migrate existing content to MongoDB ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)