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] [Resolved] (FLINK-3042) Define a way to let types create their own TypeInformation
Date Wed, 21 Sep 2016 12:15:20 GMT

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

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

Fixed in 4cc38fd36f3190f9c0066e9cf94580669b2410cf.

> Define a way to let types create their own TypeInformation
> ----------------------------------------------------------
>                 Key: FLINK-3042
>                 URL: https://issues.apache.org/jira/browse/FLINK-3042
>             Project: Flink
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.10.0
>            Reporter: Stephan Ewen
>            Assignee: Timo Walther
>             Fix For: 1.2.0, 1.0.0
> Currently, introducing new Types that should have specific TypeInformation requires
>   - Either integration with the TypeExtractor
>   - Or manually constructing the TypeInformation (potentially at every place) and using
type hints everywhere.
> I propose to add a way to allow classes to create their own TypeInformation (like a static
method "createTypeInfo()").
> To support generic nested types (like Optional / Either), the type extractor would provide
a Map of what generic variables map to what types (deduced from the input). The class can
use that to create the correct nested TypeInformation (possibly by calling the TypeExtractor
again, passing the Map of generic bindings).

This message was sent by Atlassian JIRA

View raw message