33 PM
> *To:* Hanan Yehudai
> *Cc:* user@flink.apache.org
> *Subject:* Re: tumbling event time window , parallel
>
>
>
> I would use a regular ProcessFunction, not a WindowProcessFunction.
>
>
>
> The final WM depends on how the records were partitioned at t
o:hanan.yehu...@radcom.com>>
Cc: user@flink.apache.org<mailto:user@flink.apache.org>
Subject: Re: tumbling event time window , parallel
Hi,
The paths of the files to read are distributed across all reader / source tasks
and each task reads the files in order of their modification
ks
>
>
>
> *From:* Fabian Hueske
> *Sent:* Monday, August 26, 2019 12:38 PM
> *To:* Hanan Yehudai
> *Cc:* user@flink.apache.org
> *Subject:* Re: tumbling event time window , parallel
>
>
>
> Hi,
>
>
>
> The paths of the files to read are distribute
the WM will be the highest EVENT_TIME on my
set of files..
thanks
From: Fabian Hueske
Sent: Monday, August 26, 2019 12:38 PM
To: Hanan Yehudai
Cc: user@flink.apache.org
Subject: Re: tumbling event time window , parallel
Hi,
The paths of the files to read are distributed across all reader
gt;
>
>
>
>
>
>
>
>
> *From:* Fabian Hueske
> *Sent:* Monday, August 26, 2019 11:06 AM
> *To:* Hanan Yehudai
> *Cc:* user@flink.apache.org
> *Subject:* Re: tumbling event time window , parallel
>
>
>
> Hi,
>
>
>
> C
@flink.apache.org
Subject: Re: tumbling event time window , parallel
Hi,
Can you share a few more details about the data source?
Are you continuously ingesting files from a folder?
You are correct, that the parallelism should not affect the results, but there
are a few things that can affect that:
1) non
Hi,
Can you share a few more details about the data source?
Are you continuously ingesting files from a folder?
You are correct, that the parallelism should not affect the results, but
there are a few things that can affect that:
1) non-determnistic keys
2) out-of-order data with inappropriate
