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

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

Github user twalthr commented on the issue:

    https://github.com/apache/flink/pull/2319
  
    @fhueske I updated the PR. It is now in a mergable state. I had to disable 
automatic flattening as it flattens types but does no unflattening. So if a 
composite type enters the Table API it can never leave it untouched. The SQL 
value construction `ROW(value, value)` does not work without flattening 
anymore, we have to create an optimizer rule or something similar to flatten 
this specific type. I will create a followup issue, once this is merged.


> Allow access of composite type fields
> -------------------------------------
>
>                 Key: FLINK-4294
>                 URL: https://issues.apache.org/jira/browse/FLINK-4294
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table API & SQL
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>
> Currently all Flink CompositeTypes are treated as GenericRelDataTypes. It 
> would be better to access individual fields of composite types, too. e.g.
> {code}
> SELECT composite.name FROM composites
> SELECT tuple.f0 FROM tuples
> 'f0.getField(0)
> {code}



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

Reply via email to