Hi Chirag,
How are you using Flink? Do you allow users to pass in arbitrary Avro
schemas to a Flink cluster?
If not, then I don't think the CVE applies to you. If so, then I'd imagine
that replacing the Avro 1.11.3 jar with the 1.11.4 may be a suitable
mitigation. The fix in Apache Flink only
Hi Burak,
I recommend not using Mock libraries with Scala as it does not really need
that. Just substitute the CaffeineHelper with another implementation for
tests.
You could create two implementations of the trait CacheHelper[V]:
trait CacheHelper[V] extends Serializable {
def get(id: String):
Hi Guillermo.
ORD007 is included due to "LEFT Join" logic. The LEFT JOIN keyword returns
all records from the left table, and the matching records from the right
table.
Watermark table configuration and "FOR SYSTEM_TIME AS OF" do not discard
normal LEFT join behavior here.
Best regards,
Alexey
I'm trying to understand how watermarks work in FlinkSQL. I’ve created the
following tables:
CREATE TABLE currency_rates (
currency STRING,
conversion_rate STRING,
update_time TIMESTAMP(3),
WATERMARK FOR update_time AS update_time,
PRIMARY KEY(currency) NOT ENFO
