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] [Reopened] (OAK-4582) Split Segment in a read-only and a read-write implementations
Date Tue, 24 Apr 2018 10:07:00 GMT

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

Michael Dürig reopened OAK-4582:
--------------------------------
      Assignee:     (was: Francesco Mari)

Reopening for ease of tracking technical debt.

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

Mime
View raw message