I've a simple program which takes some inputs from a command line (Socket stream) and then aggregates based on the key.
When running this program on my local machine I see some output that is counter intuitive to my understanding of windows in Flink. The start time of the Window is around the time the Functions are being evaluated. However, the window end time is around 60 s (window size) after the current time (please see below). Can someone explain this behaviour please? import org.apache.flink.api.scala._ Output windowId: -663519360 currenttime: 1465234200007 key:[a] start: 1465234200000 end: 1465234260000 diff: 60000 windowId: -663519360 currenttime: 1465234200006 key:[b] start: 1465234200000 end: 1465234260000 diff: 60000 3> Default Assigner: 1465234200010 - EventAgg(1465234200000,1465234260000,a,3) 7> Default Assigner: 1465234200010 - EventAgg(1465234200000,1465234260000,b,4) |
could you state a specific problem?
On 07.06.2016 06:40, Soumya Simanta wrote:
|
The problem is why is the window end time in the future ? For example if my window size is 60 seconds and my window is being evaluated at 3.00 pm then why is the window end time 3.01 pm and not 3.00 pm even when the data that is being evaluated falls in the window 2.59 - 3.00. Sent from my iPhone
|
Hi, I'm afraid you're running into a bug into the special processing-time window operator. A suggested workaround would be to switch to characteristic IngestionTime and use TumblingEventTimeWindows. I also open a Jira issue for the bug so that we can keep track of it: https://issues.apache.org/jira/browse/FLINK-4028 Cheers, Aljoscha On Tue, 7 Jun 2016 at 14:57 Soumya Simanta <[hidden email]> wrote:
|
Thanks for the clarification. On Tue, Jun 7, 2016 at 9:15 PM, Aljoscha Krettek <[hidden email]> wrote:
|
Free forum by Nabble | Edit this page |