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/26 14:18:19 UTC

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

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

Manfred Baedke updated OAK-2893:
--------------------------------
    Comment: was deleted

(was: [~mmarth], I'd rather make sure that a naive call to RepositoryUpgrade.copy() is an atomic operation with predictable results and I'd like to keep the public API stable. Any tools that use RepositoryUpgrade can switch the default if desirable.)

> 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
>              Labels: resilience
>
> 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)