[jira] [Resolved] (HBASE-2549) Review Trackers (column, delete, etc) on Trunk after 2248 goes in for correctness and optimal earlying-out

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

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

Jean-Daniel Cryans resolved HBASE-2549.
---------------------------------------

    Resolution: Invalid

Resolving as invalid, it's old and stale. If there's really something here that should be done let's open more specific jiras.
                
> 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
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira