kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias J. Sax (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5144) MinTimestampTracker does not correctly add timestamps lower than the current max
Date Mon, 01 May 2017 07:27:04 GMT

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

Matthias J. Sax commented on KAFKA-5144:
----------------------------------------

After digging a little deeper, partition time get's advanced as {{5, 10, 12, 12, 20, 20}}
-- thus the initial example is correct. At the same time, the last example is also correct,
however, this new partition time (that is ready one step ahead) will only be used _after_
the record got processed. Thus, time is advanced correctly.

> MinTimestampTracker does not correctly add timestamps lower than the current max
> --------------------------------------------------------------------------------
>
>                 Key: KAFKA-5144
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5144
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.2.1
>            Reporter: Michal Borowiecki
>            Assignee: Michal Borowiecki
>
> When adding elements MinTimestampTracker removes all existing elements greater than the
added element.
> Perhaps I've missed something and this is intended behaviour but I can't find any evidence
for that in comments or tests.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message