hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6245) Provide a way to load deprecated keys from other sub-projects into configuration
Date Sat, 26 Sep 2009 18:14:16 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759928#action_12759928
] 

Sanjay Radia commented on HADOOP-6245:
--------------------------------------

While I see the advantage of push over pull, this approach would require that HDFS has its
own config initialization that pushes the deprecated keys.
HDFS does not have such a thing. Not a big deal to add it to the HDFS daemons but we would
also have to add it to all the tests. ( I guess one could argue 
that tests should have moved from old keys to new keys anyway.)
It would have been better to have the deprecated keys initialized via config files - not sure
what this would entail.

> Provide a way to load deprecated keys from other sub-projects into configuration
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-6245
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6245
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Hemanth Yamijala
>
> In HADOOP-6105, we provided a method of adding deprecated keys from other sub-projects
like HDFS and Map/Reduce using a key called hadoop.conf.extra.classes. The expectation was
that this key had class names that will be statically loaded by the Configuration class and
the classes could add deprecated keys in static blocks of their classes. We discovered as
in HADOOP-6243, that the classes added could have side-effects if they, for e.g. load resources
in configuration. To unblock builds, we are disabling this feature in fixing HADOOP-6243.
However, I am opening this JIRA to follow-up on a fix for the original intention.

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


Mime
View raw message