[
https://issues.apache.org/jira/browse/HBASE-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886098#action_12886098
]
ryan rawson commented on HBASE-1517:
------------------------------------
i guess i thought the API would be cleaner with a different method instead of a
flag, but we could do the flag.
The StoreScanner would not expose the reseek() method, since it would be the
consumer of that feature, and the scanner stack above it wouldn't do such a
feature.
Given that, would it be that much more code to add reseek() to the
KeyValueScanner? It would make the code substantially cleaner, and the boolean
flag is a little opaque at first glance.
> Implement inexpensive seek operations in HFile
> ----------------------------------------------
>
> Key: HBASE-1517
> URL: https://issues.apache.org/jira/browse/HBASE-1517
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: Jonathan Gray
> Assignee: ryan rawson
> Fix For: 0.21.0
>
>
> When we early-out of a row because of columns, versions, filters, etc... we
> seek to the end of that row one key at a time. We should do the seek at the
> HFile level in cases where we would end up skipping blocks in the process.
> This will be very common in cases with relatively large rows and regex row
> filters.
> If calls that end up doing nothing are constant time, we could also call this
> to seek to the next column (or even a specific column in ExplicitTracker
> case).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
