hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8462) Custom timestamps should not be allowed to be negative
Date Tue, 30 Apr 2013 03:12:16 GMT

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

ramkrishna.s.vasudevan commented on HBASE-8462:
-----------------------------------------------

@Enis
If we are not allowing the negative timestamps, should we not allow through bulk load also?
 This change should go in the trunk version only right?
What are the cases to have a negative timestamp in any usecase- is it to have some special
entries?  
                
> Custom timestamps should not be allowed to be negative
> ------------------------------------------------------
>
>                 Key: HBASE-8462
>                 URL: https://issues.apache.org/jira/browse/HBASE-8462
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.98.0, 0.94.8, 0.95.1
>
>         Attachments: hbase-8462_v1.patch
>
>
> Client supplied timestamps should not be allowed to be negative, otherwise unpredictable
results will follow. Especially, since we are encoding the ts using Bytes.Bytes(long), negative
timestamps are sorted after positive ones. Plus, the new PB messages define ts' as uint64.

> Credit goes to Huned Lokhandwala for reporting this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message