Hi,
Yes there are plans to support early results and control the result latency
/ result completeness trade off.
However, I cannot say when these features will be available.
Best, Fabian
2018-03-19 8:14 GMT+01:00 LiYue :
> Hi ,
>
> Is there any plan to adding these features to flink SQL ?
>
> T
Hi ,
Is there any plan to adding these features to flink SQL ?
Thanks
LiYue
tig.jd.com
> 在 2018年3月14日，上午7:48，Fabian Hueske 写道：
>
> Hi,
>
> Chesnay is right.
> SQL and Table API do not support early window results and no allowed lateness
> to update results with late arriving data.
> If y
Hi,
Chesnay is right.
SQL and Table API do not support early window results and no allowed
lateness to update results with late arriving data.
If you need such features, you should use the DataStream API.
Best, Fabian
2018-03-13 12:10 GMT+01:00 Chesnay Schepler :
> I don't think you can specif
I don't think you can specify custom triggers when using purer SQL, but
maybe Fabian or Timo know a SQL way of implementing your goal.
On 12.03.2018 13:16, 李玥 wrote:
Hi Chirag,
Thank for your reply!
I found a provided ContinuousEventTimeTrigger should be worked in my
situation.
Most examples a
Hi Chirag,
Thank for your reply!
I found a provided ContinuousEventTimeTrigger should be worked in my situation.
Most examples are based on Table API like
‘ds.keyBy(0).window().trigger(MyTrigger.of())…’, But how to apply the trigger
to a pure Flink SQL Application ?
> 在 2018年3月12日，下午5:20，
Hi LiYue,
This should help : Apache Flink 1.5-SNAPSHOT Documentation: Windows
|
|
| |
Apache Flink 1.5-SNAPSHOT Documentation: Windows
|
|
|
So basically you need to register a processing time trigger at every 10 minutes
and on callback, you can FIRE the window result like this:
