hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3315) New binary file format
Date Wed, 14 May 2008 03:13:55 GMT

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

stack commented on HADOOP-3315:

Pardon me if I'm being thick but it is still not clear to me now rows and keys relate and
why we need two indices especially if "Number of key entries equals number of RO entries,
and they have 1-1 correspondence".  Is a row made of keys?  You might extend the introduction
to include explication of how they relate.

Doc. still says meta data keys and values are String. I thought above you allowed that values
could be byte arrays?

You have setMeta and then setMetaBytes?  Why not just name the second method same as first?

In your implemenation, please keep in mind that others will most likely want to extend.  You
might consider implementing TFile as an Interface with an easily subclassable or reuseable

Good stuff

> New binary file format
> ----------------------
>                 Key: HADOOP-3315
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3315
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: io
>            Reporter: Owen O'Malley
>            Assignee: Srikanth Kakani
>         Attachments: Tfile-1.pdf, TFile-2.pdf
> SequenceFile's block compression format is too complex and requires 4 codecs to compress
or decompress. It would be good to have a file format that only needs 

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

View raw message