You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Sameer Paranjpye (JIRA)" <ji...@apache.org> on 2007/06/12 20:40:26 UTC

[jira] Resolved: (HADOOP-746) CRC computation and reading should move into a nested FileSystem

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

Sameer Paranjpye resolved HADOOP-746.
-------------------------------------

       Resolution: Duplicate
    Fix Version/s: 0.12.0
         Assignee: Hairong Kuang  (was: Owen O'Malley)

This was resolved by introducing the ChecksumFilesystem in HADOOP-928

> CRC computation and reading should move into a nested FileSystem
> ----------------------------------------------------------------
>
>                 Key: HADOOP-746
>                 URL: https://issues.apache.org/jira/browse/HADOOP-746
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 0.8.0
>            Reporter: Owen O'Malley
>            Assignee: Hairong Kuang
>             Fix For: 0.12.0
>
>
> Currently FileSystem provides both an interface and a mechanism for computing and checking crc files. I propose splitting the crc code into a nestable FileSystem that like the PhasedFileSystem has a backing FileSystem. Once the Paths are converted to URI, this is fairly natural to express. To use crc files, your uris will look like:
> crc://hdfs:%2f%2fhost1:8020/ which is a crc FileSystem with an underlying file system of hdfs://host1:8020
> This will allow users to use crc files where they make sense for their application/cluster and get rid of the "raw" methods.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.