hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-61) [hbase] Create an HBase-specific MapFile implementation
Date Fri, 13 Feb 2009 07:09:59 GMT

    [ https://issues.apache.org/jira/browse/HBASE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673163#action_12673163
] 

stack commented on HBASE-61:
----------------------------

HFile is all done but for bloom filters (compression, metadata, comparators, etc). Might wait
on BF for moment.  Work is ongoing over in http://github.com/ryanobjc/hbase-rfile/ (Ryan and
Stack).  Next is making hbase use hfile.

> [hbase] Create an HBase-specific MapFile implementation
> -------------------------------------------------------
>
>                 Key: HBASE-61
>                 URL: https://issues.apache.org/jira/browse/HBASE-61
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: io
>            Reporter: Bryan Duxbury
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: cpucalltreetfile.html, hfile.patch, hfile2.patch, hfile3.patch,
longestkey.patch, tfile.patch, tfile3.patch
>
>
> Today, HBase uses the Hadoop MapFile class to store data persistently to disk. This is
convenient, as it's already done (and maintained by other people :). However, it's beginning
to look like there might be possible performance benefits to be had from doing an HBase-specific
implementation of MapFile that incorporated some precise features.
> This issue should serve as a place to track discussion about what features might be included
in such an implementation.

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


Mime
View raw message