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] Commented: (HBASE-2517) During reads when passed the specified time range, seek to next column
Date Wed, 05 May 2010 17:28:02 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864413#action_12864413

Jonathan Gray commented on HBASE-2517:

As part of this, should also make sure we are properly optimized for the case that we only
asked for versions from a single column (or multiple columns and we are on the last column
in the set).  So once we do NEXT_COL after falling outside the time range, we should realize
there are no other columns we want and early out.

> During reads when passed the specified time range, seek to next column
> ----------------------------------------------------------------------
>                 Key: HBASE-2517
>                 URL: https://issues.apache.org/jira/browse/HBASE-2517
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Jonathan Gray
>             Fix For: 0.20.5, 0.21.0
> When we are processing the stream of KeyValues in the ScanQueryMatcher, we will check
the timestamp of the current KV against the specific TimeRange.  Currently we only check if
it is in the range or not, returning SKIP if outside the range or continuing to other checks
if within the range.
> The check should actually return SKIP if the stamp is greater than the TimeRange and
NEXT_COL if the stamp is less than the TimeRange (we know we won't take anymore columns from
the current column once we are below the TimeRange).

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

View raw message