Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <20027442.546091282694618061.JavaMail.jira@thor>
Date: Tue, 24 Aug 2010 20:03:38 -0400 (EDT)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Commented: (HBASE-2549) Review Trackers (column, delete,
 etc) on Trunk after 2248 goes in for correctness and optimal earlying-out
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902179#action_12902179 ] 

Jean-Daniel Cryans commented on HBASE-2549:
-------------------------------------------

Do we have enough time do this if 0.90.0 is due for HW? Punt?

> Review Trackers (column, delete, etc) on Trunk after 2248 goes in for correctness and optimal earlying-out
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-2549
>                 URL: https://issues.apache.org/jira/browse/HBASE-2549
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.90.0
>
>
> Once we move to all Scans, the trackers could use a refresh.  There are often times where we return, for example, a MatchCode.SKIP (which just goes to the next KV not including the current one) where we could be sending a more optimal return code like MatchCode.SEEK_NEXT_ROW.
> This is a jira to review all of this code after 2248 goes in.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.