[
https://issues.apache.org/jira/browse/HBASE-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966011#action_12966011
]
fnord 999 commented on HBASE-3293:
----------------------------------
stack, not yet.
Before I attempt to dive into the sources and come up with a patch: Could there
be any reason why negative timestamps should not be allowed?
I think, the first idea of just accepting it would be much better, since
otherwise we could not save a timestamp from before 1.1.1970...
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
