Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8E11892A0 for ; Fri, 27 Jan 2012 12:44:22 +0000 (UTC) Received: (qmail 1524 invoked by uid 500); 27 Jan 2012 12:44:22 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 1374 invoked by uid 500); 27 Jan 2012 12:44:21 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 1356 invoked by uid 99); 27 Jan 2012 12:44:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jan 2012 12:44:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jan 2012 12:44:20 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 7CFD3166B36 for ; Fri, 27 Jan 2012 12:43:42 +0000 (UTC) Date: Fri, 27 Jan 2012 12:43:42 +0000 (UTC) From: "Hudson (Commented) (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1219125345.85345.1327668222514.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1384864983.77351.1327517140885.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-7993) Hadoop ignores old-style config options for enabling compressed output MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194641#comment-13194641 ] Hudson commented on HADOOP-7993: -------------------------------- Integrated in Hadoop-Hdfs-trunk #938 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/938/]) 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