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 "Amit Jain (JIRA)" <ji...@apache.org> on 2018/05/04 05:32:00 UTC

[jira] [Assigned] (OAK-7083) CompositeDataStore - ReadOnly/ReadWrite Delegate Support

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

Amit Jain reassigned OAK-7083:
------------------------------

    Assignee: Amit Jain  (was: Matt Ryan)

> CompositeDataStore - ReadOnly/ReadWrite Delegate Support
> --------------------------------------------------------
>
>                 Key: OAK-7083
>                 URL: https://issues.apache.org/jira/browse/OAK-7083
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: blob, blob-cloud, blob-cloud-azure, blob-plugins
>            Reporter: Matt Ryan
>            Assignee: Amit Jain
>            Priority: Major
>
> Support a specific composite data store use case, which is the following:
> * One instance uses no composite data store, but instead is using a single standard Oak data store (e.g. FileDataStore)
> * Another instance is created by snapshotting the first instance node store, and then uses a composite data store to refer to the first instance's data store read-only, and refers to a second data store as a writable data store
> One way this can be used is in creating a test or staging instance from a production instance.  At creation, the test instance will look like production, but any changes made to the test instance do not affect production.  The test instance can be quickly created from production by cloning only the node store, and not requiring a copy of all the data in the data store.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)