[
https://issues.apache.org/jira/browse/HADOOP-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dushyanth updated HADOOP-12533:
-------------------------------
Description:
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.
was:
Currently WASB throws a IOException in read and seek API for both Block and
Page blobs for scenarios where the back 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.
> 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)
