[
https://issues.apache.org/jira/browse/OAK-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547565#comment-14547565
]
Chetan Mehrotra commented on OAK-2626:
--------------------------------------
[~jsedding] Thanks for the details!. However I am still not clear on the
proposed changes. If we get OAK-2627 fixed then do we still require this change
which relies in internal implementation details. As post OAK-2627 the
comparison should be fast.
Or is the intention here to avoid any possible access to FileSystem which might
cause slowdown even in reference calculation?
> 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, incremental-upgrade-no-changes.png
>
>
> 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)
