hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John George (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8319) FileContext does not support setWriteChecksum
Date Fri, 27 Apr 2012 21:54:48 GMT

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

John George updated HADOOP-8319:

    Attachment: HADOOP-8319.patch

Attaching a patch that does the following:
 * Implement set {Write|Verify} Checksum for FileContext and viewFS.
 * Tests for set {Write|Verify}Checksum for FileContext and viewFS.  
 * Make a LocalFs constructor public so that it can be extended by the test.
 * remove one of the renameInternal implementation from FilterFs since it is not being overridden
by ChecksumFs.
 * Modify ChecksumFs to create checksum files only in cases when the flag was set to true.
 * Add a method to resolve a path as much as possible (in cases where the full path does not
exist). This is to support cases where a user does a set {Write|Verify} Checksum on a file
that does not exist yet. This is a valid usecase since the user should be able to write a
checksum before a file is created or verify it in cases where a file is being copied.

Appreciate reviews and open to suggestions and comments. I will also be running all the  tests
in hadoop common and posting the results here.

> FileContext does not support setWriteChecksum
> ---------------------------------------------
>                 Key: HADOOP-8319
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8319
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 3.0.0
>            Reporter: John George
>            Assignee: John George
>         Attachments: HADOOP-8319.patch
> File Context does not support setWriteChecksum and hence users trying
> to use this functionality fails.

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


View raw message