jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Ryan (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OAK-8105) [Direct Binary Access] Update to latest Azure Blob Storage SDK
Date Tue, 01 Oct 2019 22:06:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942344#comment-16942344

Matt Ryan commented on OAK-8105:

I have a mostly-working version of {{AzureDataStore}} now atop the Azure v12 SDK preview.
SAS-based authentication is working and in my branch I have extended the tests to also test
using this authentication method.

The challenge of updating an existing blob's last modified time remains.  The SDK does not
allow us to modify this property directly.  In the v8 SDK, we achieved the end goal by instructing
the service to copy the blob to itself, which had the effect of updating the last modified
time.  So far I have not been able to get this to work in the new SDKs (v10, v11, or v12)
- a 404 error is returned.  This issue has been brought up with Microsoft and we are working
on a resolution.  

> [Direct Binary Access] Update to latest Azure Blob Storage SDK
> --------------------------------------------------------------
>                 Key: OAK-8105
>                 URL: https://issues.apache.org/jira/browse/OAK-8105
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: blob-cloud-azure
>    Affects Versions: 1.10.0, 1.12.0
>            Reporter: Matt Ryan
>            Assignee: Matt Ryan
>            Priority: Major
> Since the implementation of the original AzureDataStore, the [original Azure SDK for
Java|https://github.com/Azure/azure-sdk-for-java] has been [deprecated|https://github.com/Azure/azure-sdk-for-java/blob/master/README.md]
and replaced with a [newer SDK|https://github.com/Azure/azure-storage-java] that uses a different
> The issue raised in OAK-8013 could not be properly fixed due to a bug in the original
SDK.  OAK-8104 was created for the purpose of ensuring this gets fixed properly instead of
settling for the workaround implemented with OAK-8013.  The latest Azure SDK does not exhibit
the bug that was in the original SDK, so the proper way to fix OAK-8104 is to update AzureDataStore
to use the latest Azure SDK.

This message was sent by Atlassian Jira

View raw message