hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dushyanth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12533) Introduce FileNotFoundException in WASB for read and seek API
Date Fri, 30 Oct 2015 21:35:27 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983374#comment-14983374
] 

Dushyanth commented on HADOOP-12533:
------------------------------------

[~stevel@apache.org] Thanks steve. 

For 2. Since the files are deleted and the correctness of the test depends on getting the
exception, I didn't close the streams. 

Thanks for the suggestion. I think adding the AbstractFSContract suite of tests can be done
as improvement. I would let Chris comment on this.



> 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
>            Priority: Blocker
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-12533.001.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)

Mime
View raw message