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

Da Zhou commented on HADOOP-15659:
----------------------------------

Attaching HADOOP-15659-HADOOP-15407-002.patch.
Thanks [~tmarquardt] for your review. 

 AbfsClient L48, L63: Fixed
 AbfsRestOperation: L51: removed static.  Calls to getLogger will retrieve the 
cached AbfsClient logger. 
 AbfsFileSystem: L473: Updated. Since HEAD request response won't have message 
body, so we can not check its exception based on storage error code, so I did a 
work around based on HTTP status code.

Below are the description of the code changes:
 - Added a configuration key to enable/disable retrieving usergroup info when 
initializing AzureBlobFileSystem
 - Added a configuration key to enable/disable flush operation
 - Added finalize() for AzureBlobFileSystem
 - Updated default write buffer size and read ahead queue size
 - Replaced denpendency on com.fasterxml.jackson.core with org.codehaus.jackson
 - Removed dependency on joda-time
 - Added ShellDecruptionKeyProvider
 - Fixed a bug of HTTP status code handling in AbfsRestOperation
 - Fixed a bug of percent encoding query parameter
 - Fixed a bug of async flush
 - Fixed checkstyle issues

> ABFS: Code changes for bug fix and new tests
> --------------------------------------------
>
>                 Key: HADOOP-15659
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15659
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Da Zhou
>            Assignee: Da Zhou
>            Priority: Major
>         Attachments: HADOOP-15659-HADOOP-15407-001.patch
>
>
> - add bug fixes.
> - remove unnecessary dependencies.
> - add new tests for code changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to