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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/10/03 05:51:21 UTC
[jira] [Updated] (OAK-4871) Multiplexing NodeStore
[ https://issues.apache.org/jira/browse/OAK-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra updated OAK-4871:
---------------------------------
Description:
For a variety of use cases it is useful to multiplex multiple node stores behind a single interface.
Together with [~tomek.rekawek] I have been working on a limited-purpose MultiplexingNodeStore which aims to multiplex multiple stores with the limitation that only one store may be written to, while others are read-only.
The implementation has been validated to be functional, but not yet tested for behaviour under heavy load, performance, etc.
I believe that we can still incorporate this early to make maintenance simpler and ensure that the high-level design is correct.
Link to pull request - https://github.com/apache/jackrabbit-oak/pull/55
was:
For a variety of use cases it is useful to multiplex multiple node stores behind a single interface.
Together with [~tomek.rekawek] I have been working on a limited-purpose MultiplexingNodeStore which aims to multiplex multiple stores with the limitation that only one store may be written to, while others are read-only.
The implementation has been validated to be functional, but not yet tested for behaviour under heavy load, performance, etc.
I believe that we can still incorporate this early to make maintenance simpler and ensure that the high-level design is correct.
> Multiplexing NodeStore
> ----------------------
>
> Key: OAK-4871
> URL: https://issues.apache.org/jira/browse/OAK-4871
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: Robert Munteanu
>
> For a variety of use cases it is useful to multiplex multiple node stores behind a single interface.
> Together with [~tomek.rekawek] I have been working on a limited-purpose MultiplexingNodeStore which aims to multiplex multiple stores with the limitation that only one store may be written to, while others are read-only.
> The implementation has been validated to be functional, but not yet tested for behaviour under heavy load, performance, etc.
> I believe that we can still incorporate this early to make maintenance simpler and ensure that the high-level design is correct.
> Link to pull request - https://github.com/apache/jackrabbit-oak/pull/55
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)