Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Sat, 29 Jun 2013 09:50:20 +0000 (UTC)
From: "Dave Beech (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12655342.1372428824752.187775.1372499420323@arcas>
In-Reply-To: <JIRA.12655342.1372428824752@arcas>
References: <JIRA.12655342.1372428824752@arcas>
Subject: [jira] [Updated] (CRUNCH-228) FileTargetImpl cuts off extensions of
 output files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dave Beech updated CRUNCH-228:
------------------------------

    Attachment: CRUNCH-228.patch.2

Hey Josh - it looks like you uploaded the original patch again - the two files are the same.

Here's my patch for the other way - it just changes the expected filenames for Trevni files in the tests. Was this what you were thinking? If so I'll commit this one later. 
                
> FileTargetImpl cuts off extensions of output files
> --------------------------------------------------
>
>                 Key: CRUNCH-228
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-228
>             Project: Crunch
>          Issue Type: Bug
>            Reporter: Dave Beech
>         Attachments: CRUNCH-228.patch, CRUNCH-228.patch
>
>
> Compressed files written by mapreduce often have extensions, e.g. '.deflate', '.gz' or '.snappy'. Crunch currently cuts off these extensions during the move of output files to their final destination, which is fine in some circumstances but causes problems in others. 
> For example, running 'hadoop fs -text myfile.deflate' will show the decompressed text on screen but running 'hadoop fs -text myfile' on a deflate-compressed file with no extension prints unreadable compressed data instead. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira