Re: Inconsistent Results in Event Time based Sliding Window processing

2017-02-14 Thread Nico Kruber
Hmm, without any exceptions in the logs, I'd say that you may be on the right track with elements arriving with timestamps older than the last watermark. You may play around with allowed lateness https://ci.apache.org/projects/flink/flink-docs-release-1.2/dev/ windows.html#allowed-lateness to see

Re: Inconsistent Results in Event Time based Sliding Window processing

2017-02-14 Thread Sujit Sakre
Hi Nico, Thanks for the reply. There are no exceptions or other errors in the job/task manager logs. I am running this example from Eclipse IDE with Kafka and Zookeeper running separately; in the console there are no errors shown while processing. Previously, we were missing some windows due to w

Re: Inconsistent Results in Event Time based Sliding Window processing

2017-02-14 Thread Nico Kruber
Hi Sujit, this does indeed sound strange and we are not aware of any data loss issues. Are there any exceptions or other errors in the job/taskmanager logs? Do you have a minimal working example? Is it that whole windows are not processed or just single items inside a window? Nico On Tuesday, 1

Re: inconsistent results

2016-02-16 Thread Aljoscha Krettek
Hi, I don’t know about the results but one problem I can identify is this snipped: groupBy(0).sum(2).max(2) The max(2) here is a non-parallel operation since it finds the max over all elements, not grouped by key. If you want the max to also be per-key you have to use groupBy(0).sum(2).andMax(