[ https://issues.apache.org/jira/browse/FLINK-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576429#comment-15576429 ]
ASF GitHub Bot commented on FLINK-4294: --------------------------------------- Github user fhueske commented on a diff in the pull request: https://github.com/apache/flink/pull/2319#discussion_r83492774 --- Diff: docs/dev/table_api.md --- @@ -1656,6 +1656,29 @@ temporalOverlaps(TIMEPOINT, TEMPORAL, TIMEPOINT, TEMPORAL) </td> </tr> + <tr> + <td> + {% highlight java %} +ANY.flatten() +{% endhighlight %} + </td> + <td> + <p>Converts a Flink composite type (such as Tuple, POJO, etc.) and all of its subtypes into a flat representation where every subtype is a separate field.</p> + </td> + </tr> + + <tr> + <td> + {% highlight java %} +COMPOSITE.get(STRING) --- End diff -- Didn't we agree on the symbol parsing approach like `'field$subfield`? Would that be more difficult to implement or have any other shortcomings? > 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)