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 Sami Siren <ss...@gmail.com> on 2006/08/23 17:39:52 UTC

bug or a feature?

Currently o.a.h.m.JobConf has construcor:
JobConf(Configuration conf, Class exampleClass)

which calls
    this(conf) which has
    initialize()

initialize method has:
    addDefaultResource("mapred-default.xml");

    which leads to properties of JobConf to be cleared ->
    reload is triggered.

This leads to the fact that the conf values submitted to constructor are 
not actually used, well they
kind of are for a short time because the properties are copied in 
constructor of Configuration, but then
there comes the addDefaultResource which leads to properties being 
flushed and
config resources reparsed and dynamically set values get lost.

I see that javadoc only talks about inheriting the settings, but is it 
really supposed to be working
the way it is now or should the submitted (possibly dynamically set) 
configuration variables and
values be preserved?
--
 Sami Siren




Re: bug or a feature?

Posted by Sami Siren <ss...@gmail.com>.
I now see there's a issue already open for this

https://issues.apache.org/jira/browse/HADOOP-196

--
 Sami Siren

Sami Siren wrote:
> Currently o.a.h.m.JobConf has construcor:
> JobConf(Configuration conf, Class exampleClass)
>
> which calls
>    this(conf) which has
>    initialize()
>
> initialize method has:
>    addDefaultResource("mapred-default.xml");
>
>    which leads to properties of JobConf to be cleared ->
>    reload is triggered.
>
> This leads to the fact that the conf values submitted to constructor 
> are not actually used, well they
> kind of are for a short time because the properties are copied in 
> constructor of Configuration, but then
> there comes the addDefaultResource which leads to properties being 
> flushed and
> config resources reparsed and dynamically set values get lost.
>
> I see that javadoc only talks about inheriting the settings, but is it 
> really supposed to be working
> the way it is now or should the submitted (possibly dynamically set) 
> configuration variables and
> values be preserved?
> -- 
> Sami Siren
>
>
>
>