You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2016/06/03 20:22:59 UTC
[jira] [Resolved] (KAFKA-3784) TimeWindows#windowsFor misidentifies
some windows if TimeWindows#advanceBy is used
[ https://issues.apache.org/jira/browse/KAFKA-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang resolved KAFKA-3784.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.10.0.1
Issue resolved by pull request 1462
[https://github.com/apache/kafka/pull/1462]
> TimeWindows#windowsFor misidentifies some windows if TimeWindows#advanceBy is used
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-3784
> URL: https://issues.apache.org/jira/browse/KAFKA-3784
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.0.0
> Reporter: Tom Rybak
> Assignee: Tom Rybak
> Priority: Minor
> Labels: architecture
> Fix For: 0.10.0.1
>
>
> Using a time window of size 6 minutes with a 5 minute advanceBy results in some of the timestamped data being inserted into the previous overlapping window even though the event's timestamp > that window's end time.
> The fault lies in TimeWindows#windowsFor which does not check that all the windows it's adding have an endTime > event's timestamp.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)