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/05/09 13:45:12 UTC

[jira] [Updated] (OAK-4243) Oak Segment Tar Module

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

Michael Dürig updated OAK-4243:
-------------------------------
    Epic Name: Segment Tar  (was: Segment Next)

> Oak Segment Tar Module
> ----------------------
>
>                 Key: OAK-4243
>                 URL: https://issues.apache.org/jira/browse/OAK-4243
>             Project: Jackrabbit Oak
>          Issue Type: Epic
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>             Fix For: 1.6
>
>
> There is a couple of issues requiring us to change the segment format in a non compatible way (OAK-3348, OAK-2896, OAK-2498, OAK-4201). 
> We should introduce a new module here
> * to minimise ripple effect on concurrent development work in other parts of Oak and upstream projects
> * to be able to cleanly migrate existing repositories via a side grading
> * to cleanly separate breaking changes from the existing code base
> The plan is roughly to:
> * Create new module (called {{oak-segment-next}} for now, will discuss names later)
> * Apply patch prepared for OAK-3348
> * Discuss and decide on final name and refactor accordingly 
> * Reactor affected tooling such that the targeted segment store can be specified via an option. Keep default at {{oak-segment}}.
> * Once sufficiently stabilised, deprecate {{oak-segment}}. Make this one the default in switch the default target for tooling.
> * Define and implement migration path
> I will create respective issues as needed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)