[
https://issues.apache.org/jira/browse/FLINK-18696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699564#comment-17699564
]
Timo Walther commented on FLINK-18696:
--------------------------------------
[~ungureanuserg] this is still an issue and actually a very important one. The
change itself is minimal but the biggest issue is backwards compatibility. If
the type inference becomes smarter what happens with pipeline and state that
used the old logic?
Is there a way to identify records via byte code? If yes, we could support
immutable types only for records and use Kryo for immutable types that are not
records.
> Java 14 Records are not recognized as POJOs
> -------------------------------------------
>
> Key: FLINK-18696
> URL: https://issues.apache.org/jira/browse/FLINK-18696
> Project: Flink
> Issue Type: Improvement
> Components: API / Type Serialization System
> Reporter: Robert Metzger
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> starter
>
> Having a record (https://openjdk.java.net/jeps/359) such as:
> {code}
> public record Simple(int id, String name) { }
> {code}
> Leads to this log message: "class de.robertmetzger.TableApiSql$Simple does
> not contain a setter for field id"
> I believe the PojoSerializer should be able to use records.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
