[
https://issues.apache.org/jira/browse/HADOOP-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559528#action_12559528
]
Tom White commented on HADOOP-2604:
-----------------------------------
If MapFile.Reader were an interface (or an abstract class with a no args
constructor) then BloomFilterMapFile.Reader, HalfMapFileReader and caching
Readers could be implemented as wrappers instead of in a static hierarchy. This
would make it easier to mix and match readers (e.g. with or without caching)
without passing all possible parameters in the constructor.
> [hbase] Create an HBase-specific MapFile implementation
> -------------------------------------------------------
>
> Key: HADOOP-2604
> URL: https://issues.apache.org/jira/browse/HADOOP-2604
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: Bryan Duxbury
> Priority: Minor
>
> 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.
