Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
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.
<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>
Attachments
Attachments
Issue Links
- is related to
-
HDFS-12529 Get source for config tags from file name
- Resolved
-
HADOOP-15007 Stabilize and document Configuration <tag> element
- Resolved
Activity
Field | Original Value | New Value |
---|---|---|
Description |
Proposal is to add domain tag extension to the config so that ozone can use that in its configs. For example, here is an Ozone config with domain tag. <configuration> <property> <name>ozone.enabled</name> <value>True</value> <domain> REQUIRED <domain> </property> <property> <name>dfs.cblock.trace.io</name> <value>False</value> <domain> TRACE, DEBUG <domain> </property> |
Proposal is to add domain tag extension to the config so that ozone can use that in its configs. For example, here is an Ozone config with domain tag. {code} <configuration> <property> <name>ozone.enabled</name> <value>True</value> <domain> REQUIRED <domain> </property> <property> <name>dfs.cblock.trace.io</name> <value>False</value> <domain> TRACE, DEBUG <domain> </property> {code} |
Summary | Support meta tags in Ozone configs | Support meta tags in configs |
Target Version/s | HDFS-7240 [ 12332368 ] |
Fix Version/s | HDFS-7240 [ 12332368 ] |
Affects Version/s | HDFS-7240 [ 12332368 ] |
Description |
Proposal is to add domain tag extension to the config so that ozone can use that in its configs. For example, here is an Ozone config with domain tag. {code} <configuration> <property> <name>ozone.enabled</name> <value>True</value> <domain> REQUIRED <domain> </property> <property> <name>dfs.cblock.trace.io</name> <value>False</value> <domain> TRACE, DEBUG <domain> </property> {code} |
We should add meta tag extension to the hadoop/hdfs config so that we can retrieve properties by various tags like PERFORMANCE, NAMENODE etc. Right now we don't have an option available to group or list properties related to performance or security or datanodes. 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 with meta tag. {code} <configuration> <property> <name>dfs.namenode.servicerpc-bind-host</name> <value>localhost</value> <meta> REQUIRED </meta> </property> <property> <name>dfs.namenode.fs-limits.min-block-size</name> <value> 1048576 </value> <meta> PERFORMANCE</meta> </property> <property> <name>dfs.namenode.logging.level</name> <value>Info</value> <meta> TRACE, DEBUG </meta> </property> <configuration> {code} |
Description |
We should add meta tag extension to the hadoop/hdfs config so that we can retrieve properties by various tags like PERFORMANCE, NAMENODE etc. Right now we don't have an option available to group or list properties related to performance or security or datanodes. 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 with meta tag. {code} <configuration> <property> <name>dfs.namenode.servicerpc-bind-host</name> <value>localhost</value> <meta> REQUIRED </meta> </property> <property> <name>dfs.namenode.fs-limits.min-block-size</name> <value> 1048576 </value> <meta> PERFORMANCE</meta> </property> <property> <name>dfs.namenode.logging.level</name> <value>Info</value> <meta> TRACE, DEBUG </meta> </property> <configuration> {code} |
We should add meta tag extension to the hadoop/hdfs config so that we can retrieve properties by various tags like PERFORMANCE, NAMENODE etc. Right now we don't have an option available to group or list properties related to performance or security or datanodes. 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 with meta tag. {code} <configuration> <property> <name>dfs.namenode.servicerpc-bind-host</name> <value>localhost</value> <meta> REQUIRED </meta> </property> <property> <name>dfs.namenode.fs-limits.min-block-size</name> <value> 1048576 </value> <meta> PERFORMANCE,REQUIRED</meta> </property> <property> <name>dfs.namenode.logging.level</name> <value>Info</value> <meta>HDFS, DEBUG </meta> </property> <configuration> {code} |
Description |
We should add meta tag extension to the hadoop/hdfs config so that we can retrieve properties by various tags like PERFORMANCE, NAMENODE etc. Right now we don't have an option available to group or list properties related to performance or security or datanodes. 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 with meta tag. {code} <configuration> <property> <name>dfs.namenode.servicerpc-bind-host</name> <value>localhost</value> <meta> REQUIRED </meta> </property> <property> <name>dfs.namenode.fs-limits.min-block-size</name> <value> 1048576 </value> <meta> PERFORMANCE,REQUIRED</meta> </property> <property> <name>dfs.namenode.logging.level</name> <value>Info</value> <meta>HDFS, DEBUG </meta> </property> <configuration> {code} |
We should add meta tag extension to the hadoop/hdfs config so that we can retrieve properties by various tags like PERFORMANCE, NAMENODE etc. Right now we don't have an option available to group or list properties related to performance or security or datanodes. 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 with meta tag. {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} |
Attachment | HDFS-12350.01.patch [ 12884403 ] |
Status | Open [ 1 ] | Patch Available [ 10002 ] |
Attachment |
|
Attachment | HDFS-12350.01.patch [ 12884404 ] |
Attachment |
|
Attachment | HDFS-12350.01.patch [ 12884406 ] |
Attachment |
|
Attachment | HDFS-12350.01.patch [ 12884413 ] |
Attachment |
|
Attachment | HDFS-12350.01.patch [ 12884416 ] |
Attachment | HDFS-12350.02.patch [ 12884491 ] |
Description |
We should add meta tag extension to the hadoop/hdfs config so that we can retrieve properties by various tags like PERFORMANCE, NAMENODE etc. Right now we don't have an option available to group or list properties related to performance or security or datanodes. 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 with meta tag. {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} |
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} |
Attachment | HDFS-12350.03.patch [ 12885681 ] |
Attachment |
|
Attachment | HDFS-12350.03.patch [ 12885685 ] |
Fix Version/s | 3.1.0 [ 12341434 ] | |
Hadoop Flags | Reviewed [ 10343 ] | |
Target Version/s | 3.1.0 [ 12341434 ] | |
Resolution | Fixed [ 1 ] | |
Status | Patch Available [ 10002 ] | Resolved [ 5 ] |
Link |
This issue is related to |
Fix Version/s | 3.1.0 [ 12341432 ] | |
Fix Version/s | 3.1.0 [ 12341434 ] | |
Key |
|
|
Target Version/s | 3.1.0 [ 12341434 ] | |
Issue Type | Improvement [ 4 ] | New Feature [ 2 ] |
Project | Hadoop HDFS [ 12310942 ] | Hadoop Common [ 12310240 ] |
Summary | Support meta tags in configs | Support meta tag element in Hadoop XML configurations |
Link |
This issue is related to |
HDFS-12350This message was automatically generated.