[
https://issues.apache.org/jira/browse/HDFS-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937588#comment-14937588
]
Hudson commented on HDFS-8090:
------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #1203 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/1203/])
HDFS-8090. Erasure Coding: Add RPC to client-namenode to list all (zhezhang:
rev f53e402635a990458113ba0595655751d83c02e1)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES-HDFS-EC-7285.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientNamenodeProtocolTranslatorPB.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/PBHelper.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/proto/hdfs.proto
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/erasurecode/ECSchema.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/proto/ClientNamenodeProtocol.proto
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/ClientProtocol.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSClient.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientNamenodeProtocolServerSideTranslatorPB.java
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestECSchemas.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNodeRpcServer.java
> Erasure Coding: Add RPC to client-namenode to list all ECSchemas loaded in
> Namenode.
> ------------------------------------------------------------------------------------
>
> Key: HDFS-8090
> URL: https://issues.apache.org/jira/browse/HDFS-8090
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Fix For: HDFS-7285
>
> Attachments: HDFS-8090-01.patch, HDFS-8090-02.patch,
> HDFS-8090-03.patch
>
>
> ECSchemas will be configured and loaded only at the Namenode to avoid
> conflicts.
> Client has to specify one of these schemas during creation of ecZones.
> So, add an RPC to ClientProtocol to get all ECSchemas loaded at namenode, so
> that client can choose only any one of these.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
