[
https://issues.apache.org/jira/browse/HBASE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605663#action_12605663
]
Jim Kellerman commented on HBASE-686:
-------------------------------------
Mea culpa on closing this issue too early.
The patch and test case provided do indeed demonstrate and fix the problem. All
other regression tests passed as well with the patch applied. Committed to 0.1
branch. Thanks for the contribution LN!
> MemcacheScanner didn't return the first row(if it exists), cause
> HScannerInterface's output incorrect
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-686
> URL: https://issues.apache.org/jira/browse/HBASE-686
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.1.2
> Reporter: LN
> Assignee: Jim Kellerman
> Fix For: 0.1.3
>
> Attachments: HBASE-686.patch, HBASE_686.java, HBASE_686.java,
> scanner-test-for.ver.0.2.0.dev.jar.jar, TestHMemcache.java
>
>
> HTable.obtainScanner methods should return the start row if it exists,
> although HTable's javadoc didn't clearly desc. but i found the result of
> htable scanners sometimes contain the start row, sometimes not.
> after more testing and code review, i found it should be a bug in
> HStore.Memcache.MemcacheScanner. in the constructor it set this.currentRow =
> firstRow, but when doing next(), there's a this.currentRow =
> getNextRow(this.currentRow) before fetch result.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
