[
https://issues.apache.org/jira/browse/HBASE-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477600#comment-13477600
]
Anoop Sam John commented on HBASE-6577:
---------------------------------------
bq.In HRegionScannerImpl.nextRow(...) we try the current "naive" iteration for
N KVs (let's say 100). If by then we have not reached the next row, we'll issue
a direct seek.
That way if there are few version we avoid unnecessary seeks
Lars with HBASE-6032 in trunk, will it be a problem with calls to seek? I hope
with this change now seek within same block will not have overhead. So may be
we do not need configurable KV number(like 100).. Pls correct me if my
understanding is wrong
> RegionScannerImpl.nextRow() should seek to next row
> ---------------------------------------------------
>
> Key: HBASE-6577
> URL: https://issues.apache.org/jira/browse/HBASE-6577
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.96.0
>
> Attachments: 6577-0.94.txt, 6577.txt, 6577-v2.txt, 6577-v3.txt
>
>
> RegionScannerImpl.nextRow() is called when a filter filters the entire row.
> In that case we should seek to the next row rather then iterating over all
> versions of all columns to get there.
--
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
