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 "Matt Ryan (JIRA)" <ji...@apache.org> on 2018/10/10 15:47:00 UTC
[jira] [Commented] (OAK-7818) [DirectBinaryAccess] AzureDataStore
not chaining exceptions on upload completion
[ https://issues.apache.org/jira/browse/OAK-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16645168#comment-16645168 ]
Matt Ryan commented on OAK-7818:
--------------------------------
I've assigned this to myself since I wrote the code with the bug. But if there's another Oak contributor looking for a simple way to make a contribution, feel free to coordinate with me and do the fix. It should be pretty straightforward.
> [DirectBinaryAccess] AzureDataStore not chaining exceptions on upload completion
> --------------------------------------------------------------------------------
>
> Key: OAK-7818
> URL: https://issues.apache.org/jira/browse/OAK-7818
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: blob-cloud-azure
> Affects Versions: 1.9.9
> Reporter: Matt Ryan
> Assignee: Matt Ryan
> Priority: Minor
> Labels: easyfix
>
> In {{AzureBlobStoreBackend#completeHttpUpload()}}, the code catches {{StorageException}} and {{URISyntaxException}} as thrown by the Azure SDK, but this exception is not chained in the {{DataStoreException}} that is thrown if those exceptions are caught, which makes it more difficult to diagnose the real issue behind the {{DataStoreException}}.
> This was just a simple oversight in the original implementation. We should also examine the other code related to direct binary access, both in the Azure and S3 implementations, to see if there are any other similar bugs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)