[
https://issues.apache.org/jira/browse/KAFKA-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990328#comment-15990328
]
ASF GitHub Bot commented on KAFKA-5144:
---------------------------------------
GitHub user mihbor opened a pull request:
https://github.com/apache/kafka/pull/2947
KAFKA-5144 added 2 test cases
These two newly added test cases are currently failing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mihbor/kafka patch-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2947.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2947
----
commit a8b223b92c0aec31498e0d6043c8deffb1ea21ef
Author: mihbor <mih...@users.noreply.github.com>
Date: 2017-04-30T18:24:38Z
KAFKA-5144 added 2 test cases
----
> 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)
