You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2008/06/20 03:59:45 UTC
[jira] Updated: (HBASE-613) Timestamp-anchored scanning fails to
find all records
[ https://issues.apache.org/jira/browse/HBASE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman updated HBASE-613:
--------------------------------
Status: Patch Available (was: Open)
Please review.
> Timestamp-anchored scanning fails to find all records
> -----------------------------------------------------
>
> Key: HBASE-613
> URL: https://issues.apache.org/jira/browse/HBASE-613
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Reporter: stack
> Assignee: Jim Kellerman
> Fix For: 0.2.0
>
> Attachments: 613.patch, nogood.patch, TestTimestampScanning.java, Timestamp.patch
>
>
> If I add 3 versions of a cell and then scan across the first set of added cells using a timestamp that should only get values from the first upload, a bunch are missing (I added 100k on each of the three uploads). I thought it the fact that we set the number of cells found back to 1 in HStore when we move off current row/column but that doesn't seem to be it. I also tried upping the MAX_VERSIONs on my table and that seemed to have no effect. Need to look closer.
> Build a unit test because replicating on cluster takes too much time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.