Re: [DISCUSS] FLIP-401: REST API JSON response deserialization unknown field tolerance

2023-12-11 Thread Gabor Somogyi
Thanks for the responses! I'm going to start a vote based on that... On Mon, Dec 11, 2023 at 1:13 PM Márton Balassi wrote: > +1 This greatly improves interfacing with multiple Flink versions, e.g. > upgrades from the Kubernetes Operator. > > On Mon, Dec 11, 2023 at 12:36 PM Gyula Fóra wrote: >

Re: [DISCUSS] FLIP-401: REST API JSON response deserialization unknown field tolerance

2023-12-11 Thread Márton Balassi
+1 This greatly improves interfacing with multiple Flink versions, e.g. upgrades from the Kubernetes Operator. On Mon, Dec 11, 2023 at 12:36 PM Gyula Fóra wrote: > Thanks Gabor! > > +1 from my side, this sounds like a reasonable change that will > improve integration and backward compatibility.

Re: [DISCUSS] FLIP-401: REST API JSON response deserialization unknown field tolerance

2023-12-11 Thread Gyula Fóra
Thanks Gabor! +1 from my side, this sounds like a reasonable change that will improve integration and backward compatibility. Let's keep this open for at least another day before starting the vote. Cheers, Gyula On Thu, Dec 7, 2023 at 10:48 AM Gabor Somogyi wrote: > Hi All, > > I'd like to st

[DISCUSS] FLIP-401: REST API JSON response deserialization unknown field tolerance

2023-12-07 Thread Gabor Somogyi
Hi All, I'd like to start a discussion of FLIP-401: REST API JSON response deserialization unknown field tolerance[1]. *Problem statement:* At the moment Flink is not ignoring unknown fields when parsing REST responses. An example for such a class is *JobDetailsInfo* but this applies to all othe