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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/01/08 18:04:39 UTC
[jira] [Updated] (OAK-3854) TarMK tools should check whether they
run against a matching version of the repository
[ https://issues.apache.org/jira/browse/OAK-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig updated OAK-3854:
-------------------------------
Summary: TarMK tools should check whether they run against a matching version of the repository (was: TarMK tools should check wehther they run against a matching version of the repository)
> TarMK tools should check whether they run against a matching version of the repository
> --------------------------------------------------------------------------------------
>
> Key: OAK-3854
> URL: https://issues.apache.org/jira/browse/OAK-3854
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: resilience, tooling
>
> Running tools that write into a segment store might result in unwanted upgrading if the version of the tool uses a more recent segment version than the store. E.g. off line compaction currently upgrades segment format 10 to 11.
> To protected against inadvertent upgrades, a tool should check whether the segment version of the store matches its expectation (currently 11). If not, the tool should exit with a respective warning / error. For some tools it can make sense to provide a flag (e.g. {{--force}}) to override this. With this e.g. offline compaction can still be used for upgrading a segment store if explicitly told to do so.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)