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

Hudson commented on HADOOP-15474:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14249 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/14249/])
HADOOP-15474. Rename properties introduced for <tags>. Contributed by (msingh: 
rev 57c2feb0d3ed0bb4f8642300433a35f5e28071c9)
* (edit) 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/CommonConfigurationKeysPublic.java
* (edit) hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
* (edit) 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/conf/Configuration.java
* (edit) 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/TestConfiguration.java


> Rename properties introduced for <tags>
> ---------------------------------------
>
>                 Key: HADOOP-15474
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15474
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 3.1.0
>            Reporter: Nanda kumar
>            Assignee: Zsolt Venczel
>            Priority: Major
>             Fix For: 3.2.0
>
>         Attachments: HADOOP-15474.01.patch, HADOOP-15474.02.patch
>
>
> HADOOP-15007 introduces the following two properties for tagging 
> configuration properties
> * hadoop.system.tags
> * hadoop.custom.tags
> This sounds like {{tags}} fall under {{hadoop.system}} and {{hadoop.custom}} 
> related properties, but what we really want to achieve here is to have two 
> sub-division of {{tags}} namely {{system}} and {{custom}}
> For better readability, we can rename them as
> * hadoop.tags.system
> * hadoop.tags.custom



--
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