hadoop-common-issues mailing list archives

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

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

Hemanth Yamijala commented on HADOOP-6245:

Doug, the API you suggest was already part of HADOOP-6105. So, it looks like we need no work.
I also confirmed with Amareshwari working on MAPREDUCE-849, that using the technique Doug
suggested works for including deprecated keys from other projects. So, I think we can close
this JIRA.

> 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.

View raw message