[
https://issues.apache.org/jira/browse/HBASE-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989740#comment-12989740
]
Jim R. Wilson commented on HBASE-3467:
--------------------------------------
I don't want to use negative timestamps per se. That is, I personally don't
have a use case. However, I could imagine a use where legacy data is imported
where some values are in fact negative. Interpreted as a unix timestamp (the
default ts interpretation), this would be events before the epoch.
In any case, if negative values are supported, then they ought to be *really*
supported. If the architecture changed, and values had to be non-negative
integers, that's fine too. Either way as long as it's consistent.
> Get doesn't find values with negative timestamps
> ------------------------------------------------
>
> Key: HBASE-3467
> URL: https://issues.apache.org/jira/browse/HBASE-3467
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.89.20100924
> Reporter: Jim R. Wilson
>
> Timestamps are allowed to be negative values, since they're stored as type
> long. However, using the Get object to search for versions by setting
> setMaxVersions() misses them.
> I'm not sure where this code lives, but my suspicion is that the code which
> scans for matching value timestamps has a min value of 0 when it should be
> using {{java.lang.Long.MIN_VALUE}}.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
