Re: [DISCUSS] Upgrade vendored guava dependency

2023-07-31 Thread Hong Teoh
Sorry - meant to send this to a different mailing list -.- > On 31 Jul 2023, at 15:58, Hong Teoh wrote: > > Hi all, > > The current version of guava that is vendored in Beam is > com.google.guava:guava:26.0-jre. > > This version is really old, and has active vuln

[DISCUSS] Upgrade vendored guava dependency

2023-07-31 Thread Hong Teoh
Hi all, The current version of guava that is vendored in Beam is com.google.guava:guava:26.0-jre. This version is really old, and has active vulnerabilities [1] [2] [1] https://mvnrepository.com/artifact/com.google.guava/guava/26.0-jre [2] CVE-2023-2976 https://cve.mitre.org/cgi-bin/cvename.cgi?

Re: [DISCUSS][2.0] FLIP-337: Remove JarRequestBody#programArgs

2023-07-18 Thread Hong Teoh
+1 to this. Nice to simplify the REST API! Regards, Hong > On 18 Jul 2023, at 10:00, Chesnay Schepler wrote: > > Something to note is that the UI is using this parameter, and would have to > be changed to the new one. > > Since we want to avoid having to split arguments ourselves, this may

Re: [DISCUSS] Flink REST API improvements

2023-06-26 Thread Hong Teoh
Thanks David for the feedback! > CheckpointStatsCache is also populated using the "cached execution graph," > so there is nothing to gain from the "staleness" pov; see > AbstractCheckpointHandler for more details. You are right about the CheckpointStatisticsCache. Sorry I was referring to the “

Re: [VOTE] FLIP-304: Pluggable Failure Enrichers

2023-04-20 Thread Hong Teoh
+1 (non-binding) Thank you for driving this effort, Panagiotis. Regards, Hong > On 20 Apr 2023, at 12:16, David Morávek wrote: > > Thanks for the update! > > +1 (binding) > > Best, > D. > > On Thu, Apr 20, 2023 at 9:50 AM Piotr Nowojski wrote: > >> Hi, >> >> I see that the FLIP has been

Re: [DISCUSS] FLIP-304: Pluggable failure handling for Apache Flink

2023-03-22 Thread Hong Teoh
Hi all, Thank you Panagiotis for proposing this. From the size of the thread, this is a much needed feature in Flink! Some thoughts, to extend those already adeptly summarised by Piotr, Matthias and Jing. - scope of FLIP: +1 to scoping this FLIP to observability around a restart. That would in