HBase
  1. HBase
  2. HBASE-61

[hbase] Create an HBase-specific MapFile implementation

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.20.0
    • Component/s: io
    • Labels:
      None
    • Hadoop Flags:
      Incompatible change

      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.

      1. tfile3.patch
        400 kB
        stack
      2. tfile.patch
        356 kB
        stack
      3. longestkey.patch
        2 kB
        stack
      4. hfile3.patch
        375 kB
        stack
      5. hfile2.patch
        387 kB
        stack
      6. hfile.patch
        385 kB
        stack
      7. HBASE-83.patch
        662 kB
        ryan rawson
      8. cpucalltreetfile.html
        658 kB
        stack

        Issue Links

        There are no Sub-Tasks for this issue.

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              ryan rawson
              Reporter:
              Bryan Duxbury
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development