[
https://issues.apache.org/jira/browse/HADOOP-12350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737857#comment-14737857
]
Dushyanth commented on HADOOP-12350:
------------------------------------
[~cnauroth] Thanks for the review Chris.
I see that inside NativeAzureFileSystem class there are calls to
IOUtils.cleanup(LOG, out). However IOUtils only exposes cleanup API that take
Commons Logging objects and not Slf4j objects.
considering that Hadoop community is moving towards use of Slf4j, would the
IOUtils be exposing an Api that that takes Slf4j?
If not, then I looked at the code for cleanup, it basically closes
I looked at the code for cleanup it basically closes the Closeable objects and
logs exception message on it. Do you see issues in having this implemented on
the NativeAzureFileSystem class itself and move away from using IOUtils?
> WASB Logging: Improve WASB Logging around deletes, reads and writes
> -------------------------------------------------------------------
>
> Key: HADOOP-12350
> URL: https://issues.apache.org/jira/browse/HADOOP-12350
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools
> Reporter: Dushyanth
> Assignee: Dushyanth
> Fix For: 2.8.0
>
> Attachments: 0001-HADOOP-12350-Added-WASB-Logging-Statement.patch
>
>
> Logging around the WASB component is very limited and it is disabled by
> default. This improvement is created to add logging around Reads, Writes and
> Deletes when Azure Storage Exception to capture the blobs that hit the
> exception. This information is useful while communicating with the Azure
> storage team for debugging purposes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
