kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5144) MinTimestampTracker uses confusing variable names
Date Wed, 03 May 2017 20:44:04 GMT

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

Guozhang Wang updated KAFKA-5144:
---------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

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

> MinTimestampTracker uses confusing variable names
> -------------------------------------------------
>
>                 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
>            Priority: Trivial
>             Fix For: 0.11.0.0
>
>
> --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.--
> {{MinTimestampTracker}} maintains a list of elements ascending by timestamp, but calls
the list var {{descendingSubsequence}} -- it also get the largest element at the end and stores
it in a var called {{minElem}}.



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

Mime
View raw message