[
https://issues.apache.org/jira/browse/HBASE-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222341#comment-13222341
]
Anoop Sam John commented on HBASE-5520:
---------------------------------------
We can support only seek() and reseek() at the row boundary level.
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??
4. We can give the signature of the seek() and reseek() at the RegionScanner as
seek( byte[] rowKey ) reseek( byte[] rowKey )? So that the seek will be always
to the begin KV of the row in every CF. [ if CF contains that key ]
> Support seek() reseek() at RegionScanner
> ----------------------------------------
>
> Key: HBASE-5520
> URL: https://issues.apache.org/jira/browse/HBASE-5520
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.92.0
> Reporter: Anoop Sam John
>
> seek() reseek() is not supported currently at the RegionScanner level. We can
> support the same.
> This is created following the discussion under HBASE-2038
--
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
