[
https://issues.apache.org/jira/browse/OAK-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051527#comment-14051527
]
Jukka Zitting commented on OAK-1932:
------------------------------------
So far I only expected the compactor to always start the compaction process
from the empty state, so the problem above shouldn't be an issue. But +1 on the
patch, it makes it easier to adapt the code to other use cases like backup or
to something like incremental compaction if we want to add a feature like that
later on.
> TarMK compaction can create mixed segments
> ------------------------------------------
>
> Key: OAK-1932
> URL: https://issues.apache.org/jira/browse/OAK-1932
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, segmentmk
> Affects Versions: 1.0.1
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Attachments: Compactor.java.patch, CompactorTest.java.patch
>
>
> As described in http://markmail.org/message/ujkqdlthudaortxf, commits that
> occur while the compaction operation is running can make the compacted
> segments contain references to older data segments, which prevents old data
> from being reclaimed during cleanup.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
