hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8967) Reported source for config property can be misleading
Date Fri, 08 Feb 2013 21:35:13 GMT

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

Robert Joseph Evans updated HADOOP-8967:
----------------------------------------

    Attachment: HADOOP-8967.txt

This patch cleans it up, by making it more transparent as to what Configuration itself is
doing.  The real problem now is that it now shows how convoluted some of what Configuration
does.

For example mapreduce.output.fileoutputformat.outputdir is set programmatically, but because
it is set programmatically mapred.output.dir is also set.  But when job.xml is written out
the HashMap backing Configuration will put mapred.output.dir after mapreduce.output.fileoutputformat.outputdir.
So when job.xml is read back in the source information for mapreduce.output.fileoutputformat.outputdir
indicates that it was set because mapred.output.dir was in job.xml.

I am not sure if there is a good way to not confuse customers unless we clean up Configuration
to be less confusing or we stop reporting it to end users. 
                
> Reported source for config property can be misleading
> -----------------------------------------------------
>
>                 Key: HADOOP-8967
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8967
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.23.3
>            Reporter: Jason Lowe
>            Assignee: Robert Joseph Evans
>            Priority: Minor
>         Attachments: HADOOP-8967.txt
>
>
> Configuration.set tries to track the source of a property being set, but it mistakenly
reports properties as being deprecated when they are not.  This is misleading and confusing
for users examining a job's configuration.
> For example, run a sleep job and check the job configuration on the job UI.  The source
for the "mapreduce.job.maps" property will be reported as "job.xml ⬅ because mapreduce.job.maps
is deprecated".  This leads users to think mapreduce.job.maps is now a deprecated property
and wonder what other property they should use instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message