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 "Francesco Mari (JIRA)" <ji...@apache.org> on 2016/07/20 17:50:20 UTC

[jira] [Commented] (OAK-4582) Split Segment in a read-only and a read-write implementations

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

Francesco Mari commented on OAK-4582:
-------------------------------------

The development for this issue is happening on [this branch|https://github.com/francescomari/jackrabbit-oak/tree/issues/4582] of my private fork. See the extended commit messages for further details.

> Split Segment in a read-only and a read-write implementations
> -------------------------------------------------------------
>
>                 Key: OAK-4582
>                 URL: https://issues.apache.org/jira/browse/OAK-4582
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>             Fix For: Segment Tar 0.0.8
>
>
> {{Segment}} is central to the working of the Segment Store, but it currently serves two purposes:
> # It is a temporary storage location for the currently written segment, waiting to be full and flushed to disk.
> # It is a way to parse serialzed segments read from disk.
> To distinguish these two use cases, I suggest to promote {{Segment}} to the status of interface, and to create two different implementations for a read-only and a read-write segments.



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