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] Updated: (HBASE-1202) getRow does not always work when specifying number of versions
Date Sat, 07 Mar 2009 16:48:56 GMT

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

Jim Kellerman updated HBASE-1202:
---------------------------------

         Priority: Major  (was: Blocker)
    Fix Version/s:     (was: 0.19.1)
                   0.19.2

Downgrading to major and moving 0.19.2. It can be fixed when we do scanners with multiple
versions.

> getRow does not always work when specifying number of versions
> --------------------------------------------------------------
>
>                 Key: HBASE-1202
>                 URL: https://issues.apache.org/jira/browse/HBASE-1202
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.19.0, 0.19.1, 0.20.0
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>             Fix For: 0.19.2, 0.20.0
>
>         Attachments: TestGetRowVersions.java
>
>
> When a cell that exists is updated, getRow specifying number of versions does not work.
> What is returned is the original value at that timestamp, instead of the updated value.
> Note that this only applies when more than one version is specified. getRow with (implied)
timestamp = latest does work.

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