flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timo Walther (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4783) Allow to register TypeInfoFactories manually
Date Mon, 10 Oct 2016 08:40:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15561665#comment-15561665
] 

Timo Walther commented on FLINK-4783:
-------------------------------------

Stephan and I had a discussion about globally assigned TypeInfoFactories. The reason why this
method is not public (and intended for future use of internal TypeInformation such as basic
types) is that all type extractor methods are static. Registering factories also statically
could cause unintended side effects, if the factory is registered/unregistered at wrong positions
in the code.

> Allow to register TypeInfoFactories manually
> --------------------------------------------
>
>                 Key: FLINK-4783
>                 URL: https://issues.apache.org/jira/browse/FLINK-4783
>             Project: Flink
>          Issue Type: Improvement
>          Components: Type Serialization System
>    Affects Versions: 1.2.0
>            Reporter: Till Rohrmann
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> The newly introduced {{TypeInfoFactories}} (FLINK-3042 and FLINK-3060) allow to create
{{TypeInformations}} for types which are annotated with {{TypeInfo}}. This is useful if the
user has control over the type for which he wants to generate the {{TypeInformation}}.
> However, annotating a type is not always possible if the type comes from an external
library. In this case, it would be good to be able to directly register a {{TypeInfoFactory}}
without having to annotate the type.
> The {{TypeExtractor#registerFactory}} already has such a method. However, it is declared
private.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message