hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Gray (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-2649) Make use of storefile 'order' making certain decisions during merge sort
Date Wed, 08 Sep 2010 17:32:37 GMT

     [ https://issues.apache.org/jira/browse/HBASE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Gray resolved HBASE-2649.
----------------------------------

    Hadoop Flags: [Reviewed]
      Resolution: Fixed

Fixed with HBASE-1485 commit.

> 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
>            Assignee: Pranav Khaitan
>             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.


Mime
View raw message