[
https://issues.apache.org/jira/browse/FLINK-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-12141:
-----------------------------------
Labels: pull-request-available stale-assigned starter usability (was:
pull-request-available starter usability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 14, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it. If the "warning_label" label is not removed 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)
