hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-686) MemcacheScanner didn't return the first row(if it exists), cause HScannerInterface's output incorrect
Date Mon, 16 Jun 2008 21:09:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605411#action_12605411
] 

Jim Kellerman commented on HBASE-686:
-------------------------------------

LN,

Could you please post your testcase and patch as attachments to this Jira. Jira has mangled
your input to the extent that it is difficult to make a working test program or patch out
of either of your posts.

Thanks.


> 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
>
> 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.


Mime
View raw message