[
https://issues.apache.org/jira/browse/HBASE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874357#action_12874357
]
Jonathan Gray commented on HBASE-2517:
--------------------------------------
Similar but different. This jira is specifically about some of the
QueryMatcher return codes and ensuring they are optimal and return NEXT_COL and
NEXT_ROW when appropriate given a TimeRange.
HBASE-2450 deals with actually seeking the HFile.
These two are related, however. We should be passing in stuff like NEXT_COL
and NEXT_ROW down to the HFiles to do re-seeking where appropriate (when it
means jumping to another block). There's a JIRA for that.
> 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: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Jonathan Gray
> Fix For: 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.
