[
https://issues.apache.org/jira/browse/HBASE-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221541#comment-13221541
]
Anoop Sam John commented on HBASE-2038:
---------------------------------------
@Lars
{quote}
Seeking is done one level (or two actually) level deeper.
Seeking is done in the StoreScanners, coprocessors see RegionScanners.
It is not entirely clear to me where to hook this up in that API.
{quote}
Yes at RegionScanners level we dont have seek() or reseek(). It is one level
down @ KeyValueHeap level.
Will it be correct to add seek() reseek() behaviours at RegionScanner level?[
We just need to delegate seek() or reseek() calls into KeyValueHeap object
within the RegionScanner...]
If so it would be very easy to do a reseek() to the needed row at the
coprocessor preScannerNext().
next() will take the needed row.
What do you say? Correct me if my suggestion is wrong.
> Coprocessors: Region level indexing
> -----------------------------------
>
> Key: HBASE-2038
> URL: https://issues.apache.org/jira/browse/HBASE-2038
> Project: HBase
> Issue Type: New Feature
> Components: coprocessors
> Reporter: Andrew Purtell
> Priority: Minor
>
> HBASE-2037 is a good candidate to be done as coprocessor. It also serve as a
> good goalpost for coprocessor environment design -- there should be enough of
> it so region level indexing can be reimplemented as a coprocessor without any
> loss of functionality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
