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. Regards, Salva On Sun, Apr 7, 2024 at 5:43 AM Yunfeng Zhou <flink.zhouyunf...@gmail.com> wrote: > Hi Salva, > > According to the description of the configuration > `pipeline.generic-types`, after setting this to false you should be > able to find UnsupportedOperationException in the Flink log describing > the data types that have not been supported in Kryo. Then you should > be able to look into your code finding out the usages of the certain > data type and perform corresponding bug fixes. Other information > provided in Flink's log, like those info-level logs in > TypeExtractor@analyzePojo, might help reveal more details around the > exception. > > Best, > Yunfeng > > On Wed, Apr 3, 2024 at 4:19 PM Salva Alcántara <salcantara...@gmail.com> > wrote: > > > > 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 <salcantara...@gmail.com> > wrote: > >> > >> 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 the issue, what is the simplest way to debug it? > You can of course add a breakpoint in: > >> org.apache.flink.api.java.typeutils.TypeExtractor@analyzePojo > >> > >> but ideally there should be a simpler way to show all the problems > encountered to the user without having to get that deep into the code. > >> > >> Thanks in advance, > >> > >> Salva >
