[ https://issues.apache.org/jira/browse/FLINK-36922 ]
ZhiyuanLiu deleted comment on FLINK-36922:
------------------------------------
was (Author: JIRAUSER308170):
Hi, I’d like to take up this issue as my first contribution. The task seems
manageable and I’m confident I can add the required log statement and
corresponding test.
Please let me know if there are any additional considerations or guidelines I
should follow. Thanks!
> Add warning when creating KryoSerializer for generic type
> ---------------------------------------------------------
>
> Key: FLINK-36922
> URL: https://issues.apache.org/jira/browse/FLINK-36922
> Project: Flink
> Issue Type: Improvement
> Components: API / Core
> Reporter: LEONID ILYEVSKY
> Priority: Major
>
> In
> [https://github.com/apache/flink/blob/fbf532e213882369494ee0f8595814a60de999bd/flink-core/src/main/java/org/apache/flink/api/java/typeutils/GenericTypeInfo.java#L84]
>
> the code throws an exception when the type is treated as generic and generic
> types are disabled.
> It would be very helpful if this function logged a warning every time, so
> that we can see all generic types for which KryoSerializer is used. This way
> we can enable generic types and and examine them all by looking in the log.
> So it would make sense just to add a warning log statement before line 85.
> Currently the only way to see the problematic generic type is to disable them
> and look at the exception, but this shows only the first one. We need to see
> all.
> Another workaround is to use the debugger, with breakpoint on line 85. This
> is pretty tedious, and cannot be used in runtime environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
