You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2009/06/19 17:36:10 UTC

[jira] Commented: (HBASE-1545) atomicIncrements creating new values with Long.MAX_VALUE

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

Andrew Purtell commented on HBASE-1545:
---------------------------------------

+1

> atomicIncrements creating new values with Long.MAX_VALUE
> --------------------------------------------------------
>
>                 Key: HBASE-1545
>                 URL: https://issues.apache.org/jira/browse/HBASE-1545
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: ryan rawson
>            Assignee: ryan rawson
>             Fix For: 0.20.0
>
>         Attachments: HBASE-1545.patch
>
>
> Atomic increment is creating new key values with timestamp of Long.MAX_VALUE.  This is not good, makes it hard to do range queries (as most of Thrift queries are).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.