[
https://issues.apache.org/jira/browse/HBASE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874304#action_12874304
]
stack commented on HBASE-2649:
------------------------------
@Ryan I wasn't advocating going back to old-style Gets. Storefile order is
info we can exploit under certain circumstances (e.g. my first example above
should not be contentious).
Let this issue subsume HBASE-2454 "Revisit major compaction deletes after
hbase-2248 (take storefile age into consideration)" because its more general.
There we said "See Jon's note over in HBASE-2453 on issues with deletes around
major compactions."
> 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.21.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.
