HBase
  1. HBase
  2. HBASE-2649

Make use of storefile 'order' making certain decisions during merge sort

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.90.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      When we merge sort results currently there is no regard for storefile order. This issue is about exploiting store file order at certain junctures. For example, if we have N KVs all of the same coordinates – same r/f/q/type/ts – then the one from the storefile that was made most recently should prevail. Also, we might consider order when looking at deletes so our tombstones are less tombstoney in that they'll only apply to values that are in storefiles older than the one that carries the delete marker (this latter sounds hard but putting it out there anyways).

      1. HBASE-1485-V9.patch
        43 kB
        Pranav Khaitan

        Issue Links

          Activity

          stack created issue -
          stack made changes -
          Field Original Value New Value
          Fix Version/s 0.21.0 [ 12313607 ]
          stack made changes -
          Link This issue is blocked by HBASE-2406 [ HBASE-2406 ]
          Pranav Khaitan made changes -
          Assignee Pranav Khaitan [ pranavkhaitan ]
          Jonathan Gray made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Hadoop Flags [Reviewed]
          Resolution Fixed [ 1 ]
          Pranav Khaitan made changes -
          Attachment HBASE-1485-V9.patch [ 12454750 ]

            People

            • Assignee:
              Pranav Khaitan
              Reporter:
              stack
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development