[ 
https://issues.apache.org/jira/browse/HBASE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antoni updated HBASE-686:
-------------------------

    Attachment: scanner-test-for.ver.0.2.0.dev.jar.jar

it's test case for ver 0.2.0 dev  from trunk. - sources inside the jar package

  this is class with main method which do : 
  1) creates table - if it doesn't exist
  2) create BatchUpdate with a "rowKey" and commit into a table
  3) make - getRow with "rowKey" - and shows on console data in this row
  4) make - getScanner on whole table  and shows all rows - and counts how many 
rows scanner returns

it returns :

table : testTable exists. 
 data inserted 
-------------------------------------
 getRow : 
  isEmpty = false
  row key = 0000
  col val = testvalue
-------------------------------------
 getScanner : 
scanner find : 0 rows in this table.
 done. 

 what does it mean ?
getRow can gets data by rowKey - this data exists in table, but the scanner 
doesn't see this row - and return 0 rows.

   Antoni

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

Reply via email to