jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-6941) Compatibility matrix for oak-run compact
Date Thu, 30 Nov 2017 14:23:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272720#comment-16272720

Michael Dürig commented on OAK-6941:

To start collecting data I compiled a list of Segment format versions and when these where

|| Segment Version || 10 || 11 || 12 || 13 || 
| Introduced with | Oak 1.0 | Oak 1.0.12 (OAK-2294) | Oak 1.5.2 (OAK-4232) | Oak 1.7.6 (OAK-6457)

This table does not fully determine compatibility though. Other factors to take into account
* {{oak-segment}} vs. {{oak-segment-tar}}
* Tar file structure
* {{gc.log}}
* {{journal.log}}
* ...

Given the numbers of contributors here I think it is not realistic to come up with a full
compatibility matrix. What we should try to aim for is a matrix which lists know compatibilities
and know incompatibilities. To that respect above table already answers the questions which
versions are not compatible because of changes in the segment version. 

> Compatibility matrix for oak-run compact
> ----------------------------------------
>                 Key: OAK-6941
>                 URL: https://issues.apache.org/jira/browse/OAK-6941
>             Project: Jackrabbit Oak
>          Issue Type: Documentation
>          Components: doc, run, segment-tar
>            Reporter: Valentin Olteanu
>              Labels: documentation, tooling
>             Fix For: 1.8
> h4. Problem statement
> For compacting the segmentstore using {{oak-run}}, the safest option is to use the same
version of {{oak-run}} as the Oak version used to generate the repository. Yet, sometimes,
a newer {{oak-run}} version is recommended to benefit of bug fixes and improvements, but not
every combination of source repo and oak-run is safe to use and the user needs a way to check
the compatibility. Thus, the users need a tool that guides the decision of which version to
> h4. Requirements
> * Easy to decide what {{oak-run}} version should be used for a certain Oak version
> * Up to date with the latest releases
> * Machine readable for scripting
> * Include details on the benefits of using a certain version (release notes)
> * Blacklist of versions that should not be used (with alternatives)
> h4. Solution

This message was sent by Atlassian JIRA

View raw message