flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3042) Define a way to let types create their own TypeInformation
Date Wed, 20 Jul 2016 11:51:20 GMT

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

Stephan Ewen commented on FLINK-3042:
-------------------------------------

I think this one is meant to be more of a generic version. Any time someone wants to add a
custom type that should not be a generic (Kryo) type, it would be great to be able to attach
something to the class that returns a type information.

An initial thought would be to allow for something like

{code}
@TypeInfo(MyTypeInfoFactory.class)
public class MyType {
    ....
}

public class MyTypeInfoFactory extends TypeInfoFactory<MyType> {

    public TypeInformation<MyType> createTypeInfo() {
        return ...
    }
}
{code}

> 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
>             Fix For: 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
(v6.3.4#6332)

Mime
View raw message