Hi Dominik,
I see, thanks for explaining the diagram.
This is expected because the 1 minute window in your case is aligned with the
beginning of every minute.
For example, if the first element element comes at 12:10:45, then the element
will be put in the window of 12:10:00 to 12:10:59.
Theref
> First, some remarks here - sources (in your case the Kafka consumer) will
> not stop fetching / producing data when the windows haven’t fired yet.
>
This is for sure true. However, the plot shows the number of records produced
per second, where each record was assigned a created at timestamp
Hi,
Thanks for the clarification.
What are the reasons behind consuming/producing messages from/to Kafka while
the window has not expired yet?
First, some remarks here - sources (in your case the Kafka consumer) will not
stop fetching / producing data when the windows haven’t fired yet. Does t
Hi Gordon,
The job was run using processing time. The Kafka broker version I’ve used was
0.10.1.1.
Dominik
> On 30 Mar 2017, at 08:35, Tzu-Li (Gordon) Tai wrote:
>
> Hi Dominik,
>
> Was the job running with processing time or event time? If event time, how
> are you producing the watermark
Hi Dominik,
Was the job running with processing time or event time? If event time, how are
you producing the watermarks?
Normally to understand how windows are firing in Flink, these two factors would
be the place to look at.
I can try to further explain this once you provide info with these. Al
