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

Dushyanth updated HADOOP-12533:
-------------------------------
    Attachment: HADOOP-12533.002.patch

Thanks [~cnauroth] for the quick CR.

1) I have made the change to use error codes from the Azure Storage SDK 
classes. However the Java Azure storage SDK, does not handle error codes 
consistently. In some places the error code returned back from the SDK is from 
[~StorageErrorCode] enum class 
(https://github.com/Azure/azure-storage-java/blob/9248873511c14f112fcae5f6402447a7fab76162/microsoft-azure-storage/src/com/microsoft/azure/storage/StorageErrorCode.java)
  as its the case here in [~StorageException.java] 
(https://github.com/Azure/azure-storage-java/blob/9248873511c14f112fcae5f6402447a7fab76162/microsoft-azure-storage/src/com/microsoft/azure/storage/StorageException.java#L128)
 and in some cases it is from the StorageErrorCodeStrings class. So I have 
refactored the code to handle both possible cases.

2) I have added exception message for FileNotFoundException.

3) I have added teardown method to close the inputstream after each test.

4) I will check with my manager to see if I need to pick up the adding of 
AbstractFSContract suite to WASB.

> Introduce FileNotFoundException in WASB for read and seek API
> -------------------------------------------------------------
>
>                 Key: HADOOP-12533
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12533
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 2.8.0
>            Reporter: Dushyanth
>            Assignee: Dushyanth
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-12533.001.patch, HADOOP-12533.002.patch
>
>
> Currently WASB throws a IOException in read and seek API for both Block and 
> Page blobs for scenarios where the backing blobs do not exists. This creates 
> problems for applications like HBase which expect a FileNotFoundException in 
> these scenarios. 
> The fix for the problem is to check if the exceptions from Azure storage is 
> because for Blob not found and throw FileNotFound exception if that is the 
> case.



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

Reply via email to