[HBASE-61] [hbase] Create an HBase-specific MapFile implementation

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.20.0
• Component/s: io
• Hadoop Flags: Incompatible change
• Assignee: ryan rawson
• Reporter: Bryan Duxbury
• Created: 14/Jan/08 23:20
• Updated: 13/Sep/09 22:24
• Resolved: 25/Feb/09 05:49

Description

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.

Issue Links

• incorporates: HBASE-236 NPE on failed open of region
• is blocked by: HBASE-1200 Add bloomfilters
• is related to: HBASE-1192 LRU-style map for the block cache
• is related to: HBASE-1249 Rearchitecting of server, client, API, key format, etc for 0.20
• is related to: HBASE-68 [hbase] HStoreFiles needlessly store the column family name in every entry

Sub-Tasks

• Define an interface that will apply to any possible store file implementation: Closed
• Convert existing MapFIle (or HStoreFile) to conform to new interface: Closed
• Convert HStore to use only new interface methods: Closed
• Remove the HStoreFile 'info' file (and index and bloomfilter if possible): Closed