[
https://issues.apache.org/jira/browse/HBASE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889933#action_12889933
]
Jonathan Gray commented on HBASE-2649:
--------------------------------------
I'd opt to keep this open. I feel pretty strongly that this is a good
short-term solution towards those bigger jiras. It does suggest an
implementation but the others are pretty broad... this is specific and targeted
so might be able to find someone to implement it :)
> 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.
