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

Hadoop QA commented on HDFS-10538:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s {color} 
| {color:red} HDFS-10538 does not apply to HDFS-9924. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12811212/HDFS-10538-HDFS-9924.001.patch
 |
| JIRA Issue | HDFS-10538 |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/15799/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> Remove AsyncDistributedFileSystem
> ---------------------------------
>
>                 Key: HDFS-10538
>                 URL: https://issues.apache.org/jira/browse/HDFS-10538
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: Xiaobing Zhou
>            Assignee: Xiaobing Zhou
>         Attachments: HDFS-10538-HDFS-9924.000.patch, 
> HDFS-10538-HDFS-9924.001.patch
>
>
> Per discussion in HDFS-9924,  this JIRA is to remove 
> AsyncDistributedFileSystem to make it invisible by moving it to tests, 
> however, the underlying implementation can be reused by any proposed async 
> API. It makes much sense to keep it, making it easy and possible to try on 
> various async API implementation down the road.



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

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

Reply via email to