[
https://issues.apache.org/jira/browse/FLINK-10273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598786#comment-16598786
]
Rong Rong commented on FLINK-10273:
-----------------------------------
[~twalthr] Yes I remember there are cases where resulting Composite type cannot
be further concat with composite type operations. I think one of the reason is
that the resulting type is a {{GenericType<Row>}} instead of a specific
{{RowTypeInfo}} which I had some hard time dealing with in FLINK-9294.
Another think that might have been related is: FLINK-10019 where there are some
issues with Calcite when trying to type inference a {{Struct Type}}.
I can dig deeper into this :-)
> Access composite type fields after a function
> ---------------------------------------------
>
> Key: FLINK-10273
> URL: https://issues.apache.org/jira/browse/FLINK-10273
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Affects Versions: 1.7.0
> Reporter: Timo Walther
> Priority: Major
>
> If a function returns a composite type, for example, {{Row(lon: Float, lat:
> Float)}}. There is currently no way of accessing fields.
> Both queries fail with exceptions:
> {code}
> select t.c.lat, t.c.lon FROM (select toCoords(12) as c) AS t
> {code}
> {code}
> select toCoords(12).lat
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)