Switching to the new thread...
G
On Thu, Dec 7, 2023 at 10:25 AM Gyula Fóra wrote:
> You should start a new discussion thread according to the FLIP guidelines,
> so that it's identifiable that this is a FLIP discussion.
>
> Gyula
>
> On Thu, Dec 7, 2023 at 10:22 AM Gabor Somogyi
> wrote:
>
>
You should start a new discussion thread according to the FLIP guidelines,
so that it's identifiable that this is a FLIP discussion.
Gyula
On Thu, Dec 7, 2023 at 10:22 AM Gabor Somogyi
wrote:
> Gyula, thanks for sharing your opinion.
> I've created a small FLIP as asked:
>
> https://cwiki.apach
Gyula, thanks for sharing your opinion.
I've created a small FLIP as asked:
https://cwiki.apache.org/confluence/display/FLINK/FLIP-401%3A+REST+API+JSON+response+deserialization+unknown+field+tolerance
Let's wait on voices until beginning of next week.
G
On Wed, Dec 6, 2023 at 11:05 AM Gyula Fór
Thanks G, I think this is a reasonable proposal which will increase
compatibility between different Flink clients and versions such as SQL
Gateway, CLI, Flink operator etc.
I don't really see any harm in ignoring unknown json fields globally, but
this probably warrants a FLIP and a proper vote.
C
Hi All,
Since the possible solution can have effect on all the REST response
deserialization I would like
ask for opinions.
*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 o
