[
https://issues.apache.org/jira/browse/OAK-8752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970136#comment-16970136
]
Tomek Rękawek commented on OAK-8752:
------------------------------------
No concerns here, I was thinking about it as well (for the oak-run version of
the migration tool).
> SegmentCopy should not lock/unlock source repository while 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
>
> 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)
