[
https://issues.apache.org/jira/browse/HDFS-9304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975181#comment-14975181
]
Hudson commented on HDFS-9304:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #587 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/587/])
HDFS-9304. Add HdfsClientConfigKeys class to (wheat9: rev
67e3d75aed1c1a90cabffc552d5743a69ea28b54)
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/tools/TestHdfsConfigFields.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> Add HdfsClientConfigKeys class to TestHdfsConfigFields#configurationClasses
> ---------------------------------------------------------------------------
>
> Key: HDFS-9304
> URL: https://issues.apache.org/jira/browse/HDFS-9304
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: build
> Reporter: Mingliang Liu
> Assignee: Mingliang Liu
> Fix For: 2.8.0
>
> Attachments: HDFS-9304.000.patch
>
>
> *tl;dr* Since {{HdfsClientConfigKeys}} holds client side config keys, we need
> to add this class to {{TestHdfsConfigFields#configurationClasses}}.
> Now the {{TestHdfsConfigFields}} unit test passes because {{DFSConfigKeys}}
> still contains all the client side config keys, though marked @deprecated. As
> we add new client config keys (e.g. [HDFS-9259]), the unit test will fail
> with the following error:
> {quote}
> hdfs-default.xml has 1 properties missing in class
> org.apache.hadoop.hdfs.DFSConfigKeys
> {quote}
> If the logic is to make the {{DFSConfigKeys}} and {{HdfsClientConfigKeys}}
> together cover all config keys in {{hdfs-default.xml}}, we need to put both
> of them in {{TestHdfsConfigFields#configurationClasses}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
