[ 
https://issues.apache.org/jira/browse/OAK-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017050#comment-16017050
 ] 

Tomek Rękawek edited comment on OAK-6240 at 5/19/17 8:20 AM:
-------------------------------------------------------------

I think I meant to use OAK-4626 with the MultiplexingNodeStore, which doesn't 
use the extra metadata.

I'll re-apply the patch to the oak-upgrade.


was (Author: tomek.rekawek):
I think I meant to use OAK-4626 with the MultiplexingNodeStore, which doesn't 
use the extra metadata.

I'll re-apply the patch to oak-upgrade.

> Sidegrade support for DocumentNodeStore to Secondary NodeStore
> --------------------------------------------------------------
>
>                 Key: OAK-6240
>                 URL: https://issues.apache.org/jira/browse/OAK-6240
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: documentmk, upgrade
>            Reporter: Chetan Mehrotra
>            Assignee: Tomek Rękawek
>              Labels: secondary-nodestore
>             Fix For: 1.8
>
>
> Seondary NodeStore feature (OAK-4180) currently creates the secondary 
> NodeStore upon initialization. This may take long time for existing repo. To 
> simplify that we should add support in sidegrade to migrate an existing 
> DocumentNodeStore setup to Secondary NodeStore
> This would also allow us to use the sidegraded repository as a clone of 
> existing repository with the advantage that it would support incremental 
> updates. Currently if a repository is cloned it does not support incremental 
> update as NodeState comparison is done based on default implementation 
> (actual comparison) as it cannot make use of recordId or revision to optimize 
> the diff to determine trees which are not changed between source and target



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to