hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7287) Configuration deprecation mechanism doesn't work properly for GenericOptionsParser/Tools
Date Wed, 18 May 2011 18:16:48 GMT

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

Aaron T. Myers updated HADOOP-7287:
-----------------------------------

    Attachment: hadoop-7287-trunk.0.patch

Patch for trunk which addresses the issue.

> Configuration deprecation mechanism doesn't work properly for GenericOptionsParser/Tools
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7287
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7287
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.22.0, 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Aaron T. Myers
>            Priority: Blocker
>             Fix For: 0.22.0, 0.23.0
>
>         Attachments: hadoop-7287-testcase.txt, hadoop-7287-trunk.0.patch
>
>
> For example, you can't use -D options on the "hadoop fs" command line in order to specify
the deprecated names of configuration options. The issue is that the ordering is:
> - JVM starts
> - GenericOptionsParser creates a Configuration object and calls set() for each of the
options specified on command line
> - DistributedFileSystem or other class eventually instantiates HdfsConfiguration which
adds the deprecations
> - Some class calls conf.get("new key") and sees the default instead of the version set
on the command line

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message