Thanks for driving, Qingsheng.
+1 for reverting sink metric name.
We often forget that metric is also one of the important APIs.
+1 for releasing 1.15.3 to fix this.
Best,
Jingsong
On Sun, Oct 9, 2022 at 11:35 PM Becket Qin wrote:
>
> Thanks for raising the discussion, Qingsheng,
>
> +1 on re
Hi Marco,
The progress of the release of 1.16.0 can be tracked on d...@flink.apache.org.
You can subscribe to this mail list and pay attention to related emails,
like "[summary] Flink 1.16 release sync".
As I can see there is an ongoing vote for the 1.16.0 release candidate #1,
and you may get th
Thanks for raising the discussion, Qingsheng,
+1 on reverting the breaking changes.
In addition, we might want to release a 1.15.3 to fix this and update the
previous release docs with this known issue, so that users can upgrade to
1.15.3 when they hit it. It would also be good to add some backwa
Sorry if this question was already posted
By now only a few videos of the conference were published (mainly the
keynotes)
https://www.youtube.com/playlist?list=PLDX4T_cnKjD10qp1y2B4sLNW5KL_P6RuB
Are the other presentations not going to be published?
Günter
Hello,
Does anyone know when the 1.16.0 version will be released please?
Regards.
Hi, Alexis.
I think you are right. It also applies for a global window with a custom
trigger.
If you apply a ReduceFunction or AggregateFunction, the window state size
usually is smaller than applying ProcessWindowFunction due to the
aggregated value. It also works for global windows.
Of course, th
Hi Martijn
I do not maintain a large production application based on Flink, so it
would not be a problem for me to convert existing implementations to
whatever API.
I am working in the area of cultural heritage, which is mainly about the
processing of structured (meta)-data (scientific libra
