You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2015/12/15 19:25:46 UTC

[jira] [Commented] (HADOOP-12643) Allow getmerge command to skip writing the CRC file.

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

Chris Nauroth commented on HADOOP-12643:
----------------------------------------

I don't think we can switch the default behavior of {{-getmerge}} to skip writing the CRC file.  That might cause a backwards-compatibility problem.  Instead, I think we'll need to add a {{-skipcrc}} argument that opts out of writing the CRC file.  Unfortunately, that still won't be completely consistent with {{-get}}, but at least users will have the ability to skip writing the CRC file.

We could also consider making the {{-getmerge}} and {{-get}} arguments fully consistent as a backwards-incompatible change on trunk/3.0.

> Allow getmerge command to skip writing the CRC file.
> ----------------------------------------------------
>
>                 Key: HADOOP-12643
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12643
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>            Reporter: Chris Nauroth
>
> The {{-getmerge}} shell command always write a local CRC file.  It's prefixed with a '.', so it's a hidden file and often goes unnoticed.  This behavior differs from {{-get}}, which skips writing the CRC file by default, but allows the user to opt in to writing a CRC file by passing the {{-crc}} argument.  This issue proposes adding support to {{-getmerge}} to skip writing the CRC file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)