You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/13 13:27:41 UTC

[jira] [Commented] (FLINK-5481) Simplify Row creation

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

ASF GitHub Bot commented on FLINK-5481:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/3127
  
    I think this goes into a good direction.
    I am wondering, though, if we need types like "time interval" in `flink-core`. I would prefer to keep then in the Table API scope.
    
    There can be a class `Types` in `flink-core` and one in `flink-table` - the table one extends the core one. That way you can have common types in core, extended types in table, and still get access to all by importing the `flink-table:Types` class.


> Simplify Row creation
> ---------------------
>
>                 Key: FLINK-5481
>                 URL: https://issues.apache.org/jira/browse/FLINK-5481
>             Project: Flink
>          Issue Type: Bug
>          Components: DataSet API, Table API & SQL
>    Affects Versions: 1.2.0
>            Reporter: Anton Solovev
>            Assignee: Anton Solovev
>            Priority: Trivial
>
> When we use {{ExecutionEnvironment#fromElements(X... data)}} it takes first element of {{data}} to define a type. If first Row in collection has wrong number of fields (there are nulls) TypeExtractor returns not RowTypeInfo, but GenericType<Row>



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)