[
https://issues.apache.org/jira/browse/HADOOP-8065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108043#comment-15108043
]
David Ongaro commented on HADOOP-8065:
--------------------------------------
When will this finally get merged? I was delighted to see that the Amazon
s3distcp supports output compression
(http://docs.aws.amazon.com/ElasticMapReduce/latest/ReleaseGuide/UsingEMR_s3distcp.html)
but got disappointed to see that it's not supported by the standard distcp
included in hadoop even though it can output to s3.
I think copying the data to a different storage system is a perfectly valid
(probably even common?) usecase, to have the data compressed, even though it
doesn't need to be compressed on hdfs. It's just an unnecessary step and a
waste of resources if we have to duplicate the data on hdfs in compressed form
before the distcp.
> distcp should have an option to compress data while copying.
> ------------------------------------------------------------
>
> Key: HADOOP-8065
> URL: https://issues.apache.org/jira/browse/HADOOP-8065
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 0.20.2
> Reporter: Suresh Antony
> Priority: Minor
> Labels: distcp
> Fix For: 0.20.2
>
> Attachments: HADOOP-8065-trunk_2015-11-03.patch,
> HADOOP-8065-trunk_2015-11-04.patch, patch.distcp.2012-02-10
>
>
> We would like compress the data while transferring from our source system to
> target system. One way to do this is to write a map/reduce job to compress
> that after/before being transferred. This looks inefficient.
> Since distcp already reading writing data it would be better if it can
> accomplish while doing this.
> Flip side of this is that distcp -update option can not check file size
> before copying data. It can only check for the existence of file.
> So I propose if -compress option is given then file size is not checked.
> Also when we copy file appropriate extension needs to be added to file
> depending on compression type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
