Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 30 May 2012 19:23:23 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <1054566875.17774.1338405803813.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1270306805.16403.1338388643187.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HADOOP-8449) hadoop fs -text fails with
 compressed sequence files with the codec file extension
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harsh J updated HADOOP-8449:
----------------------------

    Attachment: HADOOP-8449.patch

This patch ought to take care of this. The reverse order is what Hue does as well, as I remember from my https://issues.cloudera.org/browse/HUE-1 patch.

I could not find tests for this command (or others) so haven't added any.
                
> hadoop fs -text fails with compressed sequence files with the codec file extension
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-8449
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8449
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 1.0.3, 2.0.0-alpha
>            Reporter: Joey Echeverria
>            Priority: Minor
>         Attachments: HADOOP-8449.patch
>
>
> When the -text command is run on a file and the file ends in the default extension for a codec (e.g. snappy or gz), but is a compressed sequence file, the command will fail.
> The issue is that it assumes that if it matches the extension, then it's plain compressed file. It might be more helpful to check if it's a sequence file first, and then check the file extension second.

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