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 "Andrei Dulceanu (Jira)" <ji...@apache.org> on 2019/11/08 15:04:00 UTC

[jira] [Closed] (OAK-8752) SegmentCopy should not lock/unlock source repository before/after copying

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

Andrei Dulceanu closed OAK-8752.
--------------------------------

> SegmentCopy should not lock/unlock source repository before/after copying
> -------------------------------------------------------------------------
>
>                 Key: OAK-8752
>                 URL: https://issues.apache.org/jira/browse/OAK-8752
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-azure, segment-tar
>            Reporter: Andrei Dulceanu
>            Assignee: Andrei Dulceanu
>            Priority: Minor
>             Fix For: 1.20.0
>
>
> Since SegmentStoreMigrator already supports migrating a repository which is still written to at the time of migration, I think we should remove the unnecessary locking/unlocking before/after doing the actual copying.
> One can use {{oak-run check}} for checking the consistency of the resulted migrated repository after the migration is done, just to double-check that everything is ok.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)