{
"emoji": "",
"version": 1
}
nghao Chen
From: Salva Alcántara
Sent: Monday, April 8, 2024 16:01
To: Yunfeng Zhou
Cc: user@flink.apache.org
Subject: Re: Debugging Kryo Fallback
Yeah I think you're right and there is no need for anything, really.
I was thinking of having more user friendly tests for my POJOs f
Yeah I think you're right and there is no need for anything, really.
I was thinking of having more user friendly tests for my POJOs for which I
checked the Kryo Fallback and if detected provide an exhaustive list of
issues found (vs raising an exception for the first problem, requiring
users to
Hi Salva,
Could you please give me some hint about the issues Flink can collect
apart from the exception and the existing logs? Suppose we record the
exception in the log and the Flink job continues, I can imagine that
similar Kryo exceptions from each of the rest records will then appear
in the
Thanks Yunfeng! That is more or less what I do now when I run into the
problem. This approach reports problems one at a time (an exception is
raised on the first problem encountered).
Instead of that, I think accumulating all the issues and presenting them
all at once would be more user friendly.
FYI Reposted in SO:
-
https://stackoverflow.com/questions/78265380/how-to-debug-the-kryo-fallback-in-flink
On Thu, Mar 28, 2024 at 7:24 AM Salva Alcántara
wrote:
> I wonder which is the simplest way of troubleshooting/debugging what
> causes the Kryo fallback.
>
> Detecting it is just a matter
I wonder which is the simplest way of troubleshooting/debugging what causes
the Kryo fallback.
Detecting it is just a matter of adding this line to your job:
```
env.getConfig().disableGenericTypes();
```
or in more recent versions:
```
pipeline.generic-types: false
```
But once you detect
