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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2016/01/28 21:56:40 UTC

[jira] [Resolved] (OAK-1947) Make backup and restore options generic

     [ https://issues.apache.org/jira/browse/OAK-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Parvulescu resolved OAK-1947.
----------------------------------
    Resolution: Won't Fix

this is not realistic, for content migration between nodestores we have better options.

> Make backup and restore options generic
> ---------------------------------------
>
>                 Key: OAK-1947
>                 URL: https://issues.apache.org/jira/browse/OAK-1947
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: run
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>            Priority: Minor
>
> I'd like to refactor the backup and restore options in oak-core to use a generic NodeStore, this means making the input parameter accept a mongo connection.
> This would open the door to basic content migration between stores, one could in theory do MongoMK -- (backup) --> SegmentMK or MongoMK --(restore) --> SegmentMK. Things get a bit more complicated when there's a DataStore in place, but that should be tackled in a following issue.



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