[
https://issues.apache.org/jira/browse/OAK-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011723#comment-16011723
]
Chetan Mehrotra commented on OAK-6220:
--------------------------------------
bq. what if in the moment of switching we just get the rootState().builder()
and treat it as the copy-on-write repository
This looks promising at quick glance. Would have a closer look. [~mreutegg]
thoughts here would be helpful. Marcel the idea here is to have a temporary
repository where changes are stored locally and not made visible to other
cluster nodes. This repository is used in a transient phase and writes done
here are expected to be discarded.
> Copy on write node store implementation
> ---------------------------------------
>
> Key: OAK-6220
> URL: https://issues.apache.org/jira/browse/OAK-6220
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: Tomek Rękawek
> Fix For: 1.8
>
> Attachments: OAK-6220-2.patch, OAK-6220.patch
>
>
> The copy-on-write (COW) node store implementation would allow to temporarily
> switch the repository into the "testing" mode, in which all the changes are
> saved in a reversible way. After switching back to the "production" mode, the
> test changes should be dropped.
> This should include checkpoints as well.
> Because the SegmentNodeStore supports COW natively, we may simply copy the /
> tree to some user-provided path and use it as a new root. For the
> DocumentNodeStore we'll need something more complex.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
