Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Hadoop >> mail # dev >> Configuration and final parameters


+
Jason Lowe 2013-07-02, 14:34
Copy link to this message
-
Re: Configuration and final parameters
Given the lack of feedback, I'm guessing this is just a bug.  Filed
HADOOP-9725.

On 07/02/2013 09:34 AM, Jason Lowe wrote:
> Someone in our group recently discovered that Configuration parameters
> marked final can still be set().  The final designation only seems to
> be important when loading resources and is ignored when individual
> properties are modified.  The javadocs do call out loaded resources
> explicitly, but there's no indication as to why final properties are
> not checked during individual property modifications.  Bug or
> intentional?  Will something break if it calls set() and subsequently
> doesn't see the updated value because the final parameter silently
> ignored the new setting?
>
> The lack of checks in the set methods appear to be an oversight, but
> maybe I'm missing a use case?
>
> Jason
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB