-
> *From:* Fabian Hueske
> *Sent:* Thursday, March 15, 2018 11:55:12 AM
>
> *To:* Yan Zhou [FDS Science]
> *Cc:* user@flink.apache.org
> *Subject:* Re: flink sql: "slow" performance on Over Window aggregation
> with time attribute set to event time
>
&
: Thursday, March 15, 2018 11:55:12 AM
To: Yan Zhou [FDS Science]
Cc: user@flink.apache.org
Subject: Re: flink sql: "slow" performance on Over Window aggregation with time
attribute set to event time
I see...
Another issue might be the frequency with which you emit watermarks (in case
you use
12:02:01 PM
>
> *To:* Yan Zhou [FDS Science]
> *Cc:* user@flink.apache.org
> *Subject:* Re: flink sql: "slow" performance on Over Window aggregation
> with time attribute set to event time
>
> Hi,
>
> It is typically not a good idea to generate watermarks based on
stand.
Best
Yan
From: Fabian Hueske
Sent: Wednesday, March 14, 2018 12:02:01 PM
To: Yan Zhou [FDS Science]
Cc: user@flink.apache.org
Subject: Re: flink sql: "slow" performance on Over Window aggregation with time
attribute set to event time
Hi,
It is
> *From:* Fabian Hueske
> *Sent:* Wednesday, March 14, 2018 3:28 AM
> *To:* Yan Zhou [FDS Science]
> *Cc:* user@flink.apache.org
> *Subject:* Re: flink sql: "slow" performance on Over Window aggregation
> with time attribute set to event time
&
.org
Subject: Re: flink sql: "slow" performance on Over Window aggregation with time
attribute set to event time
Hi,
Flink advances watermarks based on all parallel source tasks. If one of the
source tasks lags behind the others, the event time progresses as determined by
the &q
Hi,
Flink advances watermarks based on all parallel source tasks. If one of the
source tasks lags behind the others, the event time progresses as
determined by the "slowest" source task.
Hence, records ingested from a faster task might have a higher processing
latency.
Best, Fabian
2018-03-14 1:
Hi,
I am using flink sql in my application. It simply reads records from kafka
source, converts to table, then runs an query to have over window aggregation
for each record. Time lag watermark assigner with 10ms time lag is used.
The performance is not ideal. the end-to-end latency, which is th
