[jira] [Commented] (HBASE-3293) Negative timestamps can be inserted without fail but not read again

["Duo Zhang (JIRA)" <ji...@apache.org>]

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

Duo Zhang commented on HBASE-3293:
----------------------------------

[~stack] Let's reuse this issus...

{quote}
Why you want to go backwards? Is Jan 1st, 1970 the time of the big bang?
{quote}
IMO, timestamp is not only used to record the operation time since it can be set by end user. For example, I want to store all the big events after earth was born and the timestamp here is the time at which the event happened. The first timestamp will be 4.6 billions years ago...

> Negative timestamps can be inserted without fail but not read again
> -------------------------------------------------------------------
>
>                 Key: HBASE-3293
>                 URL: https://issues.apache.org/jira/browse/HBASE-3293
>             Project: HBase
>          Issue Type: Bug
>         Environment: CentOS 5.5 with Cloudera's CDH3b3
>            Reporter: fnord 999
>
> When inserting a value into HBase that has a negative timestamp, such as -1, HBase inserts that value without an exception or any kind of other warning if we use the Java API. The value is written to a region and the webinterface of the regionservers shows that there is data in them. 
> However: neither a Scan nor a Get nor any other operation via MapReduce in the Shell or via Java can read that specific value out.
> There would be 2 different fixes in my opinion:
> 1. simply accept the negative timestamps consequently in read and write operations
> 2. if negative timestamps cannot be used, throw an exception when someone tries to insert an invalid timestamp



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)