[
https://issues.apache.org/jira/browse/HBASE-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226414#comment-13226414
]
stack commented on HBASE-5520:
------------------------------
{code}
+ if (kv == null) {$
+ throw new IllegalArgumentException("Row cannot be null.");$
+ }$
{code}
Should be kv cannot be null?
I don't understand what this means:
{code}
The kv that is required to seek must be given$
+ * explicitly for reseek. Should not be used to seek to a key which may come$
+ * before the current position.$
+ * Note : Recommended to use knowing how seek can be done on different kvs.$
+ * Suggested to seek to row boundaries like start of a row or end of a row.$
+ * Seeking to the middle of a row may lead to inconsistencies across stores.$
{code}
... its probably because I'm slow but I'm sure there will be slow fellows
following behind me. Is it saying you need to create a KV to do this?
How would I know what the next row is in advance? I suppose with the mvcc, you
have some hope of isolating this row... but if we are going for row
boundaries, this patch looks to be missing some heft.
> Support 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
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.96.0
>
> Attachments: HBASE-5520_1.patch, HBASE-5520_2.patch
>
>
> 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
