hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-8462) Custom timestamps should not be allowed to be negative
Date Wed, 21 Aug 2013 14:50:52 GMT

     [ https://issues.apache.org/jira/browse/HBASE-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Enis Soztutar updated HBASE-8462:
---------------------------------

    Attachment: hbase-8462_v3.patch

Rebased, addressed Ted's comments. Let's get this in. Stack +1'ed it already, so I will commit
unless objection if hadoopqa gives ok. 
                
> 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.96.0
>
>         Attachments: hbase-8462_v1.patch, hbase-8462_v2.patch, hbase-8462_v3.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