[
https://issues.apache.org/jira/browse/HBASE-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985444#action_12985444
]
Jim R. Wilson commented on HBASE-3467:
--------------------------------------
Update: it may be because TimeRange() defaults its {{minStamp}} field to a
value of {{0L}}.
Relevant code fragment:
{code:java}
public class TimeRange implements Writable {
private long minStamp = 0L;
private long maxStamp = Long.MAX_VALUE;
private boolean allTime = false;
{code}
Maybe it should be changed to this?
{code:java}
public class TimeRange implements Writable {
private long minStamp = Long.MIN_VALUE;
private long maxStamp = Long.MAX_VALUE;
private boolean allTime = false;
{code}
> 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.
-
You can reply to this email to add a comment to the issue online.
