[
https://issues.apache.org/jira/browse/HBASE-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222300#comment-13222300
]
Anoop Sam John commented on HBASE-2038:
---------------------------------------
@Lars
I have created HBASE-5520 for the support for seek() and reseek() at the
RegionScanner. As I mentioned in the comment we need row boundary seeks only.
Yes it might be complex wrt the other kind of seeks. We can support only seek()
and reseek() at the row boundary level only at the RegionScanner?
We can take any of the below approaches
1. The APIs make use of the rowkey and timestamp only from the KeyValue passed.
2. Check at the RegionScannerImpl level that it is not having the CF, qualifier
in the passed KV. If so throw exception. Only the KV can have the rowkey and
timestamp also.[It is ok.Timestamp can be there...]
3. Dont bother let the seek happen. But may be dangerous??
Pls give ur valuable suggestions
Me and Ram started working with this.
>From the co processor preNext() we can call reseek with
>KeyValue.createFirstOnRow(final byte [] row)
> 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
