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 "Amit Jain (JIRA)" <ji...@apache.org> on 2016/11/24 05:02:58 UTC

[jira] [Resolved] (OAK-5146) S3 getOrCreateReferenceKey() should provide a default implementation

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

Amit Jain resolved OAK-5146.
----------------------------
       Resolution: Fixed
    Fix Version/s: 1.6

Done in trunk with http://svn.apache.org/viewvc?rev=1771076&view=rev

> S3 getOrCreateReferenceKey() should provide a default implementation
> --------------------------------------------------------------------
>
>                 Key: OAK-5146
>                 URL: https://issues.apache.org/jira/browse/OAK-5146
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: blob
>            Reporter: Amit Jain
>            Assignee: Amit Jain
>             Fix For: 1.6, 1.5.15
>
>
> S3Backend#getOrCreateReferenceKey() should delegate to super to provide a transient key to be used for hashing for AbstractDataRecord#getReference if no {{secret}} key is configured. The absence of a {{secret}} key should be logged though to warn in cases where a shared secret key is essential to enable binary less replication scenarios.



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