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-4582) Split Segment in a read-only and a read-write implementations
Date Wed, 20 Jul 2016 20:33:20 GMT

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

Michael Dürig commented on OAK-4582:
------------------------------------

Interesting approach. I have yet to look at your branch, but IIUC this is about separating
the read and write concerns of segments. I think this is a good idea and it should allow us
to further decouple our code base later on.

> 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)

Mime
View raw message