[
https://issues.apache.org/jira/browse/HBASE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889686#action_12889686
]
stack commented on HBASE-2649:
------------------------------
Thinking on it, let me close this issue. Its an issue that suggests an
implementation for dealing with hbase-1485 and a newly added issue, HBASE-2847
(We can argue in HBASE-2406 if HBASE-2847 is a 'bug' or not).
> Make use of storefile 'order' making certain decisions during merge sort
> ------------------------------------------------------------------------
>
> Key: HBASE-2649
> URL: https://issues.apache.org/jira/browse/HBASE-2649
> Project: HBase
> Issue Type: Improvement
> Reporter: stack
> Fix For: 0.90.0
>
>
> 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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
