[ 
https://issues.apache.org/jira/browse/HDFS-12350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anu Engineer updated HDFS-12350:
--------------------------------
          Resolution: Fixed
        Hadoop Flags: Reviewed
       Fix Version/s: 3.1.0
    Target Version/s: 3.1.0
              Status: Resolved  (was: Patch Available)

[~ajayydv] Thank you for the contribution, I have committed this to the trunk.  
Will reopen this later to port to 3.0 branch.

> Support meta tags in configs
> ----------------------------
>
>                 Key: HDFS-12350
>                 URL: https://issues.apache.org/jira/browse/HDFS-12350
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Ajay Kumar
>            Assignee: Ajay Kumar
>             Fix For: 3.1.0
>
>         Attachments: HDFS-12350.01.patch, HDFS-12350.02.patch, 
> HDFS-12350.03.patch
>
>
> We should tag the hadoop/hdfs config so that we can retrieve properties by 
> there usage/application like PERFORMANCE, NAMENODE etc. Right now we don't 
> have an option available to group or list related properties together. 
> Grouping properties through some restricted set of Meta tags and then 
> exposing them in Configuration class will be useful for end users.
> For example, here is an config file with tags.
> {code}
> <configuration>
>    <property>
>       <name>dfs.namenode.servicerpc-bind-host</name>
>       <value>localhost</value>
>       <tag> REQUIRED </tag>
>    </property>
>    
>   <property>
>       <name>dfs.namenode.fs-limits.min-block-size</name>
>       <value> 1048576 </value>
>       <tag> PERFORMANCE,REQUIRED</tag>
>    </property>
>  <property>
>       <name>dfs.namenode.logging.level</name>
>       <value>Info</value>
>       <tag>HDFS, DEBUG </tag>
>    </property>
>       
> <configuration>
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to