[
https://issues.apache.org/jira/browse/FLINK-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329507#comment-17329507
]
Flink Jira Bot commented on FLINK-12141:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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: YangFei
> Priority: Minor
> Labels: pull-request-available, stale-assigned, starter,
> usability
> 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)
