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 "Tomek Rękawek (Jira)" <ji...@apache.org> on 2019/09/23 09:54:00 UTC
[jira] [Commented] (OAK-8640) Allow to only copy last journal entry
in the SegmentStoreMigrator
[ https://issues.apache.org/jira/browse/OAK-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935701#comment-16935701 ]
Tomek Rękawek commented on OAK-8640:
------------------------------------
Fixed for trunk in [r1867372|https://svn.apache.org/r1867372].
> Allow to only copy last journal entry in the SegmentStoreMigrator
> -----------------------------------------------------------------
>
> Key: OAK-8640
> URL: https://issues.apache.org/jira/browse/OAK-8640
> Project: Jackrabbit Oak
> Issue Type: Story
> Components: segment-azure
> Reporter: Tomek Rękawek
> Priority: Major
>
> In the oak-segment-azure, reading the whole journal may be a time consuming task, as the blob appends are a bit slow to read. The OAK-8604 introduces an improvement, by keeping the most recent journal entry saved as a metadata in the journal.log blob. We should allow to use this optimization in SegmentStoreMigrator, by adding a new migration parameter - {{onlyLastJournalEntry}}. This way, only the last entry in the journal will be migrated and it won't require to read the whole journal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)