[
https://issues.apache.org/jira/browse/HBASE-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250321#comment-15250321
]
Enis Soztutar commented on HBASE-3293:
--------------------------------------
Timestamp is an unsigned long. You can store and interpret it in whatever way
you want. You can represent any time in any time/date scheme you want. If you
leave it to HBase handle it for you, you must accept the epoch semantics with
ms resolution. No need to change anything other than enforcing timestamp being
an unsigned long.
> 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)
