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 "Francesco Mari (JIRA)" <ji...@apache.org> on 2018/01/26 10:40:00 UTC

[jira] [Assigned] (OAK-6058) Avoid accessing remote binaries when migration involves S3

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

Francesco Mari reassigned OAK-6058:
-----------------------------------

    Assignee: Francesco Mari

> Avoid accessing remote binaries when migration involves S3
> ----------------------------------------------------------
>
>                 Key: OAK-6058
>                 URL: https://issues.apache.org/jira/browse/OAK-6058
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: upgrade
>            Reporter: Tomek Rękawek
>            Assignee: Francesco Mari
>            Priority: Major
>
> When migrating (sidegrade) a repository referencing the S3DataStore, we should avoid accessing the binaries themselves and use their identifiers instead.
> In particular:
> * it should be possible to copy a a nodestore referencing S3DataStore without accessing/configuring S3 at all (copy binaries by the references),
> * if the S3DataStore is configured for the migration and the destination already exists, the blob identifiers should be used in the equals() method, not the whole binary input stream.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)