You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2016/09/21 12:16:20 UTC

[jira] [Resolved] (FLINK-3060) Add possibility to integrate custom types into the TypeExtractor

     [ https://issues.apache.org/jira/browse/FLINK-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther resolved FLINK-3060.
---------------------------------
       Resolution: Fixed
         Assignee: Timo Walther
    Fix Version/s: 1.2.0

This has been fixed as part of FLINK-3042.

> Add possibility to integrate custom types into the TypeExtractor
> ----------------------------------------------------------------
>
>                 Key: FLINK-3060
>                 URL: https://issues.apache.org/jira/browse/FLINK-3060
>             Project: Flink
>          Issue Type: New Feature
>          Components: Type Serialization System
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> As discussed in [FLINK-3002]. It would be nice if we could make custom type integration easier by defining an interface/static method that classes can implement to create their own type information. That gives users an easy extension point.
> Custom integrated types need to be checked in `getForObject`, `getForClass` and `validateInput`. If we also want to support custom integrated types with generics `createTypeInfoWithTypeHierarchy` needs modifications, too.



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