[
https://issues.apache.org/jira/browse/HADOOP-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HADOOP-7287:
--------------------------------
Attachment: hadoop-7287-testcase.txt
Here's a test case which illustrates why this problem happens. You can easily
reproduce from the command line by trying something like:
./bin/hadoop fs -Ddfs.block.size=4096 -touchz f1
./bin/hadoop fs -stat "%o" f1
and you'll see that the deprecated option was ignored and there was no warning.
> 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
> Reporter: Todd Lipcon
> Priority: Blocker
> Fix For: 0.22.0
>
> Attachments: hadoop-7287-testcase.txt
>
>
> 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
