hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoyu Yao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12608) Fix exception message in WASB when connecting with anonymous credential
Date Wed, 30 Dec 2015 19:12:49 GMT

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

Xiaoyu Yao updated HADOOP-12608:
--------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.8.0
           Status: Resolved  (was: Patch Available)

Thanks [~dchickabasapa] for the contribution and all for the reviews. I've commit the patch
to trunk, branch-2 and branch-2.8.

> Fix exception message in WASB when connecting with anonymous credential
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-12608
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12608
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 2.8.0
>            Reporter: Dushyanth
>            Assignee: Dushyanth
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-12608.001.patch, HADOOP-12608.002.patch, HADOOP-12608.003.patch,
HADOOP-12608.004.patch, HADOOP-12608.005.patch
>
>
> Users of WASB have raised complaints over the error message returned back from WASB when
they are trying to connect to Azure storage with anonymous credentials. Current implementation
returns the correct message when we encounter a Storage exception, however for scenarios like
querying to check if a container exists does not throw a StorageException but returns false
when URI is directly specified (Anonymous access) the error message returned does not clearly
state that credentials for storage account is not provided. This JIRA tracks the fix the error
message to return what is returned when a storage exception is hit and also correct spelling
mistakes in the error message.



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

Mime
View raw message