Matt Ryan commented on OAK-7083:

The following pull requests have been created for this issue:
 * [https://github.com/apache/jackrabbit-oak/pull/71] - Changes made to 
{{oak-blob-plugins}} and {{oak-blob}} to support {{CompositeDataStore}}.  This 
includes the following:

 ** Adding a {{DataStoreProvider}} interface to {{oak-blob}} so that delegate 
data stores can associate a role to themselves.
 ** Implementing {{AbstractDataStoreFactory}} in {{oak-blob-plugins}} so 
multiple data stores can be configured as factory classes.
 ** Implementing {{FileDataStoreFactory}} in {{oak-blob-plugins}} to provide 
this capability for {{FileDataStore}}.
 - Changes made to {{oak-blob-plugins}} to {{MarkSweepGarbageCollector}} so 
that garbage collection will work for {{CompositeDataStore}}.
 * [https://github.com/apache/jackrabbit-oak/pull/74] - Includes the following 
 ** Addition of {{S3DataStoreFactory}} to {{oak-blob-cloud}}
 ** Creation of {{oak-blob-composite}} which implements {{CompositeDataStore}} 
(service, data store, supporting code, unit tests, etc.)


> 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: Matt Ryan
>            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

Reply via email to