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/05/20 20:06:00 UTC

[jira] [Comment Edited] (OAK-2893) RepositoryUpgrade.copy() should optionally continue on errors.

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

Manfred Baedke edited comment on OAK-2893 at 5/20/15 6:05 PM:
--------------------------------------------------------------

Basic support: implemented in trunk with revision 1680633.
Adjusting primary types of potentially inconsistent nodes: implemented in trunk with revision 1680643.


was (Author: baedke):
Basic support implemented in trunk with revision 1680633.

> RepositoryUpgrade.copy() should optionally continue on errors.
> --------------------------------------------------------------
>
>                 Key: OAK-2893
>                 URL: https://issues.apache.org/jira/browse/OAK-2893
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: upgrade
>            Reporter: Manfred Baedke
>            Assignee: Manfred Baedke
>
> Currently RepositoryUpgrade.copy() fails on the first error. In practice this is very inconvenient, because any minor inconsistency in the source repository may cause the upgrade to fail.
> An option to make best-effort copies is needed.



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