rmoff
03/24/2025, 9:26 AM<https://nightlies.apache.org/flink/flink-docs-release-2.0/release-notes/flink-2.0/>
are 404 - is this because they are still being published? /cc @weijie guoGrzegorz Liter
03/24/2025, 11:16 AMwatermarkGenerator =
emitProgressiveWatermarks
? watermarkStrategy.createWatermarkGenerator(this::getMetricGroup)
: new NoWatermarksGenerator<>();
to
watermarkGenerator =
emitProgressiveWatermarks
? watermarkStrategy.createWatermarkGenerator(
new WatermarkGeneratorSupplier.Context() {
@Override
public MetricGroup getMetricGroup() {
return this.getMetricGroup();
}
@Override
public RelativeClock getInputActivityClock() {
return inputActivityClock;
}
})
: new NoWatermarksGenerator<>();
Where this.getMetricGroup
refereed to parent class instance before and now refers to anonymous class instance which leads to infinite recursion.
https://issues.apache.org/jira/browse/FLINK-37545AK
03/25/2025, 8:33 AMMounika Bathina
04/01/2025, 10:59 AMThomas Cooper
04/01/2025, 12:14 PM4.0-SNAPSHOT
, but I think if we are moving to the next major release for the Kafka connector it makes sense to also move to the Kafka 4.0 client libraries as they drop support for Kafka <2.1 (a breaking change). I have a PR open for that update.
I which case do we want to do a Flink Connector Kafka version 3.5 release which maintains the support for Kafka 2.0 and lower and also supports flink 2.0.0?Prashant Singh
04/01/2025, 3:45 PMAndrea Sella
04/02/2025, 8:24 AMIlya Soin
04/03/2025, 7:19 AMkim
04/03/2025, 3:30 PMHugo Polsinelli
04/04/2025, 8:05 AMMounika Bathina
04/07/2025, 6:48 AMSanil
04/07/2025, 9:55 PMKeith Lee
04/08/2025, 6:45 PMJulian Lawrence
04/08/2025, 6:51 PMKeith Lee
04/09/2025, 7:51 AMAshok
04/10/2025, 1:39 PMBhargava Sharma
04/22/2025, 12:23 AMpranav tiwari
05/02/2025, 2:16 PMAvi Sanwal
05/19/2025, 12:19 PMflink
in the entrypoint script: https://github.com/apache/flink-docker/blob/6e226503dbb228467905c70ccfb6f33f4c676872/1.20/scala_2.12-java17-ubuntu/docker-entrypoint.sh#L37.
Gosu itself is tagged by popular scanners as being vulnerable due to outdated golang usage (though author claims that gosu itself is not).
My question is, why do we need gosu to switch to flink
user and not use USER flink:flink
or something similar in Dockerfile
? This way we could avoid depending on gosu, and present a cleaner scan result.liu ron
05/28/2025, 5:52 AMHenk van Dyk
06/02/2025, 1:08 PMG
06/04/2025, 7:54 AMrmoff
06/23/2025, 1:37 PMArun Lakshman Ravichandran
06/23/2025, 6:39 PMThomas Cooper
06/24/2025, 1:43 PMVikas Patil
06/24/2025, 3:19 PMRyan van Huuksloot
06/25/2025, 4:29 AMFerenc Csaky
06/25/2025, 5:35 AMChris Harm
07/01/2025, 1:59 PM