hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ryan rawson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1792) [Regression] Cannot save timestamp in the future
Date Tue, 25 Aug 2009 20:29:59 GMT

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

ryan rawson commented on HBASE-1792:
------------------------------------

we should move back to Long.MAX_VALUE as the thing to replace to 'now' i think... 

The problem with deletes would be if the delete is set too far in the past or future, depending
on the time range of the files that end up bracketing them. Solved with minor compaction,
and works via scans.



> [Regression] Cannot save timestamp in the future
> ------------------------------------------------
>
>                 Key: HBASE-1792
>                 URL: https://issues.apache.org/jira/browse/HBASE-1792
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: Jean-Daniel Cryans
>
> 0.20, compared to previous versions, doesn't let you save with a timestamp in the future
and will set it to current time without telling you. This is really bad for users upgrading
to 0.20 that were using those timestamps.
> Example:
>  hbase(main):004:0> put 'testtable', 'r1', 'f1:c1', 'val', 5373965335336911168
>  0 row(s) in 0.0070 seconds
>  hbase(main):005:0> scan 'testtable'
>  ROW                          COLUMN+CELL                                           
                          
>   r1                          column=f1:c1, timestamp=1251223892010, value=val      
                          
>  1 row(s) in 0.0380 seconds

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message