[
https://issues.apache.org/jira/browse/HADOOP-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985539#comment-14985539
]
Dushyanth commented on HADOOP-12533:
------------------------------------
[~cnauroth] I see that Hadoop QA run failed in mvninstall subsystem. The
failure seems to be in hadoop-common. The only change between the previous
patch and this one was making close() synchronized. Which I doubt would have
any effect on mvninstall. Is this a legitimate issue or a transient failure?
[~Steve Loughran] This is hitting a bit of deadline for a release, so it would
be great if we can get a review from you. Sorry for the inconvenience.
> 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,
> HADOOP-12533.003.patch, HADOOP-12533.004.patch, HADOOP-12533.005.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)
