t; Theo
>
>
> [1]
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/SQL-Do-Not-Support-Custom-Trigger-td20932.html
>
> - Ursprüngliche Mail -
> Von: "张静"
> An: "Austin Cawley-Edwards"
> CC: "M Singh" , "user"
Trigger-td20932.html
- Ursprüngliche Mail -
Von: "张静"
An: "Austin Cawley-Edwards"
CC: "M Singh" , "user"
Gesendet: Freitag, 14. Mai 2021 06:06:33
Betreff: Re: Apache Flink - A question about Tables API and SQL interfaces
Hi Mans,
+1 for Aus
Hi Mans,
+1 for Austin's reply.
I would like to add something about "allow lateness".
After introduce Windowing table-valued function in Flink 1.13,
User could use two SQL solution to do window aggregate. And 'allow
lateness' behavior is different in these two solutions.
1. If ad
Hi Mans,
There are currently no public APIs for doing so, though if you're willing
to deal with some breaking changes there are some experimental config
options for late events in the Table API and SQL, seen in the
WIndowEmitStrategy class[1].
Best,
Austin
[1]:
https://github.com/apache/flink/bl
Thanks Austin for your helpful references.
I did take a look at [2]/[3] - but did not find anything relevant on searching
for string 'late' (for allowed lateness etc) or side output. So from my
understanding the late events will be dropped if I am using Table API or SQL
and the only option is
Hi Mans,
I don't believe there are explicit triggers/evictors/timers in the Table
API/ SQL, as that is abstracted away from the lower-level DataStream API.
If you need to get into the fine-grained details, Flink 1.13 has made some
good improvements in going from the Table API to the DataStream API
Hey Folks:
I have the following questions regarding Table API/SQL in streaming mode:
1. Is there is a notion triggers/evictors/timers when using Table API or SQL
interfaces ?2. Is there anything like side outputs and ability to define
allowed lateness when dealing with the Table API or SQL interf
