jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1947) Make backup and restore options generic
Date Tue, 08 Jul 2014 13:03:04 GMT

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

Alex Parvulescu commented on OAK-1947:
--------------------------------------

Currently moving the content from TarMK to MongoMK is not possible because the #restore operation
doesn't work. 
It could be as simple as running restore and using the TarMK folder as a source and the mongodb
connection as a destination, but it looks like there's a piece still missing, this is the
error:
{code}
Exception in thread "main" java.lang.IllegalArgumentException: builder must be a org.apache.jackrabbit.oak.plugins.document.DocumentRootBuilder
	at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.asDocumentRootBuilder(DocumentNodeStore.java:1658)
	at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.merge(DocumentNodeStore.java:1291)
	at org.apache.jackrabbit.oak.plugins.backup.FileStoreRestore.restore(FileStoreRestore.java:71)
	at org.apache.jackrabbit.oak.plugins.backup.FileStoreRestore.restore(FileStoreRestore.java:59)
	at org.apache.jackrabbit.oak.run.Main.restore(Main.java:205)
	at org.apache.jackrabbit.oak.run.Main.main(Main.java:118)
{code}


> 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.2#6252)

Mime
View raw message