You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2008/11/07 18:52:46 UTC

[jira] Created: (HADOOP-4617) hadoop-default.xml should not be in conf/ directory

hadoop-default.xml should not be in conf/ directory
---------------------------------------------------

                 Key: HADOOP-4617
                 URL: https://issues.apache.org/jira/browse/HADOOP-4617
             Project: Hadoop Core
          Issue Type: Improvement
          Components: conf
            Reporter: Doug Cutting


It is error prone to keep hadoop-default.xml in the conf/ directory.  Folks copy configuration directories between releases, but this file is strongly tied to a particualr release and should not be either editted or used with other than the release it comes with.

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


[jira] Commented: (HADOOP-4617) hadoop-default.xml should not be in conf/ directory

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646958#action_12646958 ] 

Doug Cutting commented on HADOOP-4617:
--------------------------------------

> Do I understand correctly that hadoop-default will be in HADOOP_HOME/build/classes and hadoop-site will be still in HADOOP_HOME/conf?

Yes, that is the proposal.  Defaults are for documentation only.  Putting them in the user's conf directory causes folks to use the wrong version of the defaults, since conf directories are copied between releases.  The defaults should be more strongly tied to each release.

> hadoop-default.xml should not be in conf/ directory
> ---------------------------------------------------
>
>                 Key: HADOOP-4617
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4617
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Doug Cutting
>
> It is error prone to keep hadoop-default.xml in the conf/ directory.  Folks copy configuration directories between releases, but this file is strongly tied to a particualr release and should not be either editted or used with other than the release it comes with.

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


[jira] Commented: (HADOOP-4617) hadoop-default.xml should not be in conf/ directory

Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646635#action_12646635 ] 

Konstantin Shvachko commented on HADOOP-4617:
---------------------------------------------

I also had to deal with a lot of cases when people just forgot to upgrade their default configuration. So it would be good to have some automation for that, but there is challenge here imo. It will be even harder to understand the dependencies between different configuration files if people don't see hadoop-default.xml and hadoop-site.xml together in the same directory.

> hadoop-default.xml should not be in conf/ directory
> ---------------------------------------------------
>
>                 Key: HADOOP-4617
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4617
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Doug Cutting
>
> It is error prone to keep hadoop-default.xml in the conf/ directory.  Folks copy configuration directories between releases, but this file is strongly tied to a particualr release and should not be either editted or used with other than the release it comes with.

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


[jira] Commented: (HADOOP-4617) hadoop-default.xml should not be in conf/ directory

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645838#action_12645838 ] 

Doug Cutting commented on HADOOP-4617:
--------------------------------------

We should move the master version of hadoop-default.xml to src/.  In release builds, folks should receive it through the released jar file.  It should arrive on developers' classpath by being copied to the build/classes directory.


> hadoop-default.xml should not be in conf/ directory
> ---------------------------------------------------
>
>                 Key: HADOOP-4617
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4617
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Doug Cutting
>
> It is error prone to keep hadoop-default.xml in the conf/ directory.  Folks copy configuration directories between releases, but this file is strongly tied to a particualr release and should not be either editted or used with other than the release it comes with.

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


[jira] Commented: (HADOOP-4617) hadoop-default.xml should not be in conf/ directory

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646660#action_12646660 ] 

Doug Cutting commented on HADOOP-4617:
--------------------------------------

> It will be even harder to understand the dependencies between different configuration files if people don't see hadoop-default.xml and hadoop-site.xml together in the same directory.

The defaults are documented in html that's included with each release:

http://hadoop.apache.org/core/docs/current/hadoop-default.html

Folks can refer to this to find what the default values are, no?


> hadoop-default.xml should not be in conf/ directory
> ---------------------------------------------------
>
>                 Key: HADOOP-4617
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4617
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Doug Cutting
>
> It is error prone to keep hadoop-default.xml in the conf/ directory.  Folks copy configuration directories between releases, but this file is strongly tied to a particualr release and should not be either editted or used with other than the release it comes with.

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


[jira] Commented: (HADOOP-4617) hadoop-default.xml should not be in conf/ directory

Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646735#action_12646735 ] 

Konstantin Shvachko commented on HADOOP-4617:
---------------------------------------------

Sure the fields are documented. I am talking only about the location of the configs.
Now it is rather simple go to HADOOP_HOME/conf and you see all config files there. If you separate them the users will be confused.
Do I understand correctly that hadoop-default will be in HADOOP_HOME/build/classes and hadoop-site will be still in HADOOP_HOME/conf?

> hadoop-default.xml should not be in conf/ directory
> ---------------------------------------------------
>
>                 Key: HADOOP-4617
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4617
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Doug Cutting
>
> It is error prone to keep hadoop-default.xml in the conf/ directory.  Folks copy configuration directories between releases, but this file is strongly tied to a particualr release and should not be either editted or used with other than the release it comes with.

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