[
https://issues.apache.org/jira/browse/FLINK-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597484#comment-16597484
]
Hequn Cheng commented on FLINK-9391:
------------------------------------
[~SokolovMS] Hi, I think we don't need to add an UNNEST operator. We can add a
build-in unnest table function. Currently, there are no build-in table
functions in Flink. You probably need to find a good way to implement it
without any examples. However, there are build-in scalar functions and build-in
aggregate functions(see FunctionCatalog class) and you can take a look how they
are implemented.
I just take a look at the relevant code. Similar to
Aggregation(org.apache.flink.table.expressions.Aggregation), maybe we can add
another Expression type, say TableFunction Expression which can return a
tableFunctionCall.
> Support UNNEST in Table API
> ---------------------------
>
> Key: FLINK-9391
> URL: https://issues.apache.org/jira/browse/FLINK-9391
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: Alina Ipatina
> Priority: Major
>
> FLINK-6033 introduced the UNNEST function for SQL. We should also add this
> function to the Table API to keep the APIs in sync.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
