[
https://issues.apache.org/jira/browse/FLINK-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nico Kruber closed FLINK-12141.
-------------------------------
Fix Version/s: 1.14.0
Release Note: @TypeInfo annotations can now also be used on POJO fields
which, for example, can help to define custom serializers for third-party
classes that can otherwise not be annotated themselves.
Resolution: Fixed
Fixed on master via d326b0574a373bd5eef63a44261f8762709265f8
> Allow @TypeInfo annotation on POJO field declarations
> -----------------------------------------------------
>
> Key: FLINK-12141
> URL: https://issues.apache.org/jira/browse/FLINK-12141
> Project: Flink
> Issue Type: New Feature
> Components: API / Type Serialization System
> Reporter: Gyula Fora
> Assignee: Nico Kruber
> Priority: Minor
> Labels: auto-unassigned, pull-request-available, starter,
> usability
> Fix For: 1.14.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The TypeInfo annotation is a great way to declare serializers for custom
> types however I feel that it's usage is limited by the fact that it can only
> be used on types that are declared in the project.
> By allowing the annotation to be used on field declarations we could improve
> the TypeExtractor logic to use the type factory when creating the
> PojoTypeInformation.
> This would be a big improvement as in many cases classes from other libraries
> or collection types are used within custom Pojo classes and Flink would
> default to Kryo serialization which would hurt performance and cause problems
> later.
> The current workaround in these cases is to implement a custom serializer for
> the entire pojo which is a waste of effort when only a few fields might
> require custom serialization logic.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
