Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
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).
Attachments
Attachments
Issue Links
- is blocked by
-
HBASE-2406 Define semantics of cell timestamps/versions
-
- Closed
-