[
https://issues.apache.org/jira/browse/HBASE-9000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807674#comment-13807674
]
Lars Hofhansl commented on HBASE-9000:
--------------------------------------
I've been thinking about declaring a reseek as "near" or "far". A "near" reseek
would be to the next column or row, whereas a "far" reseek could be result of a
seek hint from the Filter. In the "near" case we could try next() a few times
without and then seek, in the "far" case we'd seek immediately as we expect to
be able to skip a lot of KVs.
> Linear reseek in Memstore
> -------------------------
>
> Key: HBASE-9000
> URL: https://issues.apache.org/jira/browse/HBASE-9000
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.89-fb
> Reporter: Shane Hogan
> Priority: Minor
> Fix For: 0.89-fb
>
>
> This is to address the linear reseek in MemStoreScanner. Currently reseek
> iterates over the kvset and the snapshot linearly by just calling next
> repeatedly. The new solution is to do this linear seek up to a configurable
> maximum amount of times then if the seek is not yet complete fall back to
> logarithmic seek.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
