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

Julian Sedding updated OAK-2626:
--------------------------------
    Description: 
In OAK-2619 I propose to support repeated upgrades into the same NodeStore.

This issue does not optimizate the first run, but any subsequent run benefits 
from the proposed changes.

One use-case for this feature is to import all content several days before the 
upgrade and then copy only the delta on the day of the upgrade.

Assuming that both the source and target repositories use the same 
FileDataStore, binaries could be efficiently compared by their references.


  was:
In OAK-2619 I propose to support multiple upgrades into the same NodeStore.

One use-case for this feature is to import all content several days before the 
upgrade and then copy only the delta on the day of the upgrade.

Assuming that both the source and target repositories use the same 
FileDataStore, binaries could be efficiently compared by their references.



> Optimize binary comparison for merge during upgrade 
> ----------------------------------------------------
>
>                 Key: OAK-2626
>                 URL: https://issues.apache.org/jira/browse/OAK-2626
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: upgrade
>    Affects Versions: 1.1.7
>            Reporter: Julian Sedding
>            Priority: Minor
>         Attachments: OAK-2626.patch
>
>
> In OAK-2619 I propose to support repeated upgrades into the same NodeStore.
> This issue does not optimizate the first run, but any subsequent run benefits 
> from the proposed changes.
> One use-case for this feature is to import all content several days before 
> the upgrade and then copy only the delta on the day of the upgrade.
> Assuming that both the source and target repositories use the same 
> FileDataStore, binaries could be efficiently compared by their references.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to