[
https://issues.apache.org/jira/browse/HADOOP-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876805#action_12876805
]
Erik Steffl commented on HADOOP-6756:
-------------------------------------
Patch
https://issues.apache.org/jira/secure/attachment/12446625/HADOOP-6756-0.22.0-1.patch
resolves issues of previous patch as described in comment
https://issues.apache.org/jira/browse/HADOOP-6756?focusedCommentId=12876461&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12876461
Description of changes:
1,2: we decided upon default values for previously commented out fields, all
new config parameters are uncommented now
3: fixed
4: done
5: new description, hopefully it makes sense now
6: "{...@docroot}/../core-default.html" is used to refer to core-default.xml,
it's a document created by ant docs (forrest generated docs)
7: made the comment clear
> Clean up and add documentation for configuration keys in
> CommonConfigurationKeys.java
> -------------------------------------------------------------------------------------
>
> Key: HADOOP-6756
> URL: https://issues.apache.org/jira/browse/HADOOP-6756
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.20.3, 0.22.0
> Reporter: Erik Steffl
> Fix For: 0.20.3, 0.22.0
>
> Attachments: HADOOP-6756-0.22.0-1.patch, HADOOP-6756-0.22.0.patch,
> jira.HADOOP-6756-0.20-1-FS_DEFAULT_NAME_KEY.patch,
> jira.HADOOP-6756-0.20-1.patch, jira.HADOOP-6756-0.20.patch
>
>
> Configuration keys in CommonConfigurationKeys.java should be cleaned up and
> documented (javadoc comments, appropriate *-default.xml descriptions).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
