[
https://issues.apache.org/jira/browse/HADOOP-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010713#comment-13010713
]
Daryn Sharp commented on HADOOP-7178:
-------------------------------------
The getlocal method is returning a LocalFileSystem, so if "fs" is declared as
such, could the cast be removed?
Regarding the getVerifyChecksum(), my concern is it's semantically wrong for
all filesystems to claim (by default) that checksum files are supported. The
default should be the truth. Granted, the implementation is backwards
compatible, but future callers may operation on false assumptions of crc files.
Would it be better to default as false in FileSystem, and ChecksumFileSystem
overrides for true? I think this would also retain backwards compatibility?
> copyToLocal API is creating .crc files in local, even after setting
> verifyChecksum to false at client side.
> -----------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-7178
> URL: https://issues.apache.org/jira/browse/HADOOP-7178
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Attachments: HADOOP-7178_COMMON.patch, HADOOP-7178_HDFS.patch
>
>
> When we copy the files from DFS to local, it is creating the .crc file in
> local filesystem for the verification of checksum even if we disable the
> checksum verification at client side.
> When user does not want to do any checksum verification, then what
> will be the use in creating of these files in local file system.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
