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

Hudson commented on HADOOP-7993:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #1601 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1601/])
    HADOOP-7993. Hadoop ignores old-style config options for enabling 
compressed output. (Anupam Seth via mahadev)

mahadev : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1236506
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/conf/Configuration.java
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/TestDeprecatedKeys.java

                
> Hadoop ignores old-style config options for enabling compressed output
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-7993
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7993
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.23.1
>            Reporter: Anupam Seth
>            Assignee: Anupam Seth
>             Fix For: 0.23.1
>
>         Attachments: HADOOP-7993_branch_0_23.patch, 
> HADOOP-7993_branch_0_23.patch
>
>
> Hadoop seems to ignore the config options even though they are printed as 
> deprecation warnings in the log: mapred.output.compress and
> mapred.output.compression.codec
> - settings that work on 0.20 but not on 0.23
> mapred.output.compress=true
> mapred.output.compression.codec=org.apache.hadoop.io.compress.BZip2Codec
> - settings that work on 0.23
> mapreduce.output.fileoutputformat.compress=true
> mapreduce.output.fileoutputformat.compress.codec=org.apache.hadoop.io.compress.BZip2Codec
> This breaks backwards compatibility and causes existing jobs to fail.
> This was found to happen due to the JobSubmitter writing out the job.xml file 
> with the old-style configs and can be fixed by handdling deprecation before 
> the file is written out.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to