[
https://issues.apache.org/jira/browse/OAK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200190#comment-16200190
]
Raul Hudea commented on OAK-6802:
---------------------------------
On Azure, it might be possible to mitigate multiple writes by using an
exclusive write lease on the blob
(https://docs.microsoft.com/en-us/azure/storage/common/storage-concurrency?toc=%2fazure%2fstorage%2fblobs%2ftoc.json#managing-concurrency-in-blob-storage).
> Manage 'secret' property internally in S3/AzureDataStore
> --------------------------------------------------------
>
> Key: OAK-6802
> URL: https://issues.apache.org/jira/browse/OAK-6802
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob-cloud, blob-cloud-azure
> Reporter: Amit Jain
> Assignee: Amit Jain
> Fix For: 1.8
>
>
> Property 'secret' is required to be configured (which is a shared secret
> among instances sharing the datastore) to enable binary-less replication. The
> DataStore should manage it internally as it does for other things in the META
> folder like in the container like repository ID etc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
