[jira] [Commented] (HADOOP-12533) Introduce FileNotFoundException in WASB for read and seek API

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran commented on HADOOP-12533:
-----------------------------------------

# nice to see a concurrency test in there
# I don't see any test cleanup though....shouldn't those input streams be closed?

If you're finding and fixing bits where azure storage client behaves differently from HDFS, I'd recommend you consider implementing the  {{AbstractFSContract}} suite of tests for WASB, as I don't see it there right now. It does do seek testing, including the various corner cases ... and could have found this mismatch. (actually, I'm not sure what the other filesystems do if you rename a file that's being read, usually that's a "things may fail, failure modes undefined).



> 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
>
>
> 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)