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 2018/02/26 12:43:01 UTC

[jira] [Resolved] (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:all-tabpanel ]

Francesco Mari resolved OAK-4582.
---------------------------------
    Resolution: Later

> 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: Task
>          Components: segment-tar
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>            Priority: Major
>              Labels: technical_debt
>         Attachments: benchmark-01.png, benchmark-01.txt
>
>
> {{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
(v7.6.3#76005)