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

Hadoop QA commented on HDFS-5549:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12615405/HDFS-5549.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5548//console

This message is automatically generated.

> Support for implementing custom FsDatasetSpi from outside the project
> ---------------------------------------------------------------------
>
>                 Key: HDFS-5549
>                 URL: https://issues.apache.org/jira/browse/HDFS-5549
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 3.0.0
>            Reporter: Ignacio Corderi
>         Attachments: HDFS-5549.patch
>
>
> Visibility for multiple methods and a few classes got changed to public to 
> allow FsDatasetSpi<T> and all the related classes that need subtyping to be 
> fully implemented from outside the HDFS project.
> Blocks transfers got abstracted to a factory given that the behavior will be 
> changed for DataNodes using Kinetic drives. The existing DataNode to DataNode 
> block transfer functionality got moved to LegacyBlockTransferer, no new 
> configuration is needed to use this class and have the same behavior that is 
> currently present.
> DataNodes have an additional configuration key 
> DFS_DATANODE_BLOCKTRANSFERER_FACTORY_KEY to override the default block 
> transfer behavior.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to