hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-1824) [stargate] default timestamp should be LATEST_TIMESTAMP
Date Thu, 10 Sep 2009 19:42:57 GMT

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

Andrew Purtell resolved HBASE-1824.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0

Committed to branch and trunk.

> [stargate] default timestamp should be LATEST_TIMESTAMP
> -------------------------------------------------------
>
>                 Key: HBASE-1824
>                 URL: https://issues.apache.org/jira/browse/HBASE-1824
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 0.20.1, 0.21.0
>
>         Attachments: HBASE-1824.patch
>
>
> From Greg Cottman up on hbase-user@
> {quote}
> f I don't put the optional "timestamp" attribute in a Cell when I'm inserting data, the
timestamp ends up as zero, which caused much confusion because it pre-dates the value I thought
I was replacing.  I assumed that not specifying this attribute would cause the timestamp to
default to the current HBase server time.  Instead I found I had to specify the timestamp
as "-1" to get this behaviour.  Is this a bug or an intentional semantic?
> {quote}

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