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 2014/02/03 09:50:09 UTC

[jira] [Resolved] (OAK-1357) Add 'restore' method to NodeStore apis

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

Alex Parvulescu resolved OAK-1357.
----------------------------------

    Resolution: Not A Problem

As proposed I'm introducing a util class (OAK-1380), no need to change the apis, so I'm closing this issue.

> Add 'restore' method to NodeStore apis
> --------------------------------------
>
>                 Key: OAK-1357
>                 URL: https://issues.apache.org/jira/browse/OAK-1357
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>         Attachments: FileStoreRestore.java.patch
>
>
> OAK-762 introduced a checkpoint mechanism which allows for the creation of a snapshot of the current state, referenced by a string.
> Other than internally for the async indexing I'd like to leverage this in the case of an external (non blocking!) backup process (for both mongomk and rdbstore) and probably for the tarmk simple failover scenario.
> What is currently missing is an option to restore the current state to a captured snapshot, which is the point of this issue.
> I'm proposing we add a _ #restore(String checkpoint)_ method to the NodeStore apis which resets the current head to the provided state. 
> This could probably throw an exception in the case the provided checkpoint doesn't exist, and it would also fail ongoing transactions as they don't apply anymore.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)