[jira] [Resolved] (OAK-788) File backend for the SegmentMK

["Jukka Zitting (JIRA)" <ji...@apache.org>]

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

Jukka Zitting resolved OAK-788.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8

The basic functionality is now there, so resolving this as fixed with further improvements to be tracked in followup issues.
                
> File backend for the SegmentMK
> ------------------------------
>
>                 Key: OAK-788
>                 URL: https://issues.apache.org/jira/browse/OAK-788
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>              Labels: TarMK
>             Fix For: 0.8
>
>
> The SegmentMK now has two backends: one in-memory and the other based on MongoDB. Since MongoDB isn't readily available everywhere and the in-memory backend obviously isn't suited for production use, it would be useful to have an additional SegmentMK backend based on just the local file system.
> Inspired by, though not directly based on, the proprietary TarPM in CRX, I propose to implement such a backend using the tar file format as the basis.
> Unlike the MongoDB backend or the original TarPM, such a "TarMK" backend would be designed primarily for optimum performance on a *single-node* deployment, i.e. without support for clustering. A typical deployment could be replicated set of independent copies of a repository, designed for massively parallel read-only or mostly-read workloads.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira