Thanks for the clarification.
On Tue, Jun 7, 2016 at 9:15 PM, Aljoscha Krettek
wrote:
> 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.
>
>
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/jir
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 iP
could you state a specific problem?
On 07.06.2016 06:40, Soumya Simanta wrote:
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 m
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 tim
