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 2020/04/07 10:54:00 UTC

[jira] [Resolved] (OAK-8836) oak-run compact should offer the possibility to choose between checkpoints compactor and the classical compactor

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

Andrei Dulceanu resolved OAK-8836.
----------------------------------
    Resolution: Fixed

Fixed in trunk at r1876227.

> oak-run compact should offer the possibility to choose between checkpoints compactor and the classical compactor
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: OAK-8836
>                 URL: https://issues.apache.org/jira/browse/OAK-8836
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: oak-run, segment-tar
>            Reporter: Andrei Dulceanu
>            Assignee: Andrei Dulceanu
>            Priority: Major
>
> Until the final fix for OAK-8832 will be out and even after that, I think we must offer the possibility to do offline compaction in two modes:
> * current optimized solution which compacts checkpoints on top of the other, chronologically and after that the root state on top of those
> * previous un-optimized solution which blindly compacts everything, making use of the deduplication caches to control checkpoints "explosion"
> I propose to add an optional argument to compact, {{--compactor}} with three values: auto, diff and classic. When not set, it will just go with whatever we choose as auto - for now "classic". If set, it will use the mode provided.



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