[jira] [Resolved] (KAFKA-3716) Check against negative timestamps

["Guozhang Wang (JIRA)" <ji...@apache.org>]

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

Guozhang Wang resolved KAFKA-3716.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.1.0

Issue resolved by pull request 1393
[https://github.com/apache/kafka/pull/1393]

> Check against negative timestamps
> ---------------------------------
>
>                 Key: KAFKA-3716
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3716
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>              Labels: architecture, user-experience
>             Fix For: 0.10.1.0
>
>
> Although currently we do not enforce any semantic meaning on the {{Long}} typed timestamps, we are actually assuming it to be non-negative while storing the timestamp in windowed store. For example, in {{RocksDBWindowStore}} we store the timestamp as part of the key, and relying on RocksDB's default lexicographic byte array comparator, and hence negative long value stored in RocksDB will cause the range search ordering to be messed up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)