You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2010/05/21 14:14:16 UTC

[jira] Created: (HADOOP-6783) Rename core-* configuration files to common-*

Rename core-* configuration files to common-*
---------------------------------------------

                 Key: HADOOP-6783
                 URL: https://issues.apache.org/jira/browse/HADOOP-6783
             Project: Hadoop Common
          Issue Type: Bug
          Components: conf
            Reporter: Chris Douglas
             Fix For: 0.21.0


To reflect the name of the project, the {{core-site.xml}} and {{core-default.xml}} configuration files should be renamed to {{common-}} and the references in documentation (including javadoc) should be updated. Compatibility should be maintained, with a warning.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-6783) Rename core-* configuration files to common-*

Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870145#action_12870145 ] 

Enis Soztutar commented on HADOOP-6783:
---------------------------------------

If we are going to change the conf file name for core, then it will be nice if we rename it to hadoop-common-site.xml rather than common-site.xml. For all the projects using Hadoop, a file name starting with hadoop will make more sense. This is not that much important for mapred and hdfs, but having a file name core-site.xml reveals no clue about belonging to hadoop. 

> Rename core-* configuration files to common-*
> ---------------------------------------------
>
>                 Key: HADOOP-6783
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6783
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Chris Douglas
>             Fix For: 0.21.0
>
>
> To reflect the name of the project, the {{core-site.xml}} and {{core-default.xml}} configuration files should be renamed to {{common-}} and the references in documentation (including javadoc) should be updated. Compatibility should be maintained, with a warning.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-6783) Rename core-* configuration files to common-*

Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870085#action_12870085 ] 

Allen Wittenauer commented on HADOOP-6783:
------------------------------------------

While splitting the config may have made things easier for devs (maybe? is there any evidence that having xxx-xxx.xml did?), it would be MUCH easier from an ops and end user perspective if this was one big file again. Pushing around 3 files instead of 1 adds extra coordination and esp confusion for new users.  [I've lost track of how many times users tried to connect the hdfs client to the nn web ui port.]

If we want to retain the semi-autonomy, we could make stanzas for each project.



> Rename core-* configuration files to common-*
> ---------------------------------------------
>
>                 Key: HADOOP-6783
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6783
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Chris Douglas
>             Fix For: 0.21.0
>
>
> To reflect the name of the project, the {{core-site.xml}} and {{core-default.xml}} configuration files should be renamed to {{common-}} and the references in documentation (including javadoc) should be updated. Compatibility should be maintained, with a warning.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.