[
https://issues.apache.org/jira/browse/FLINK-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957211#comment-15957211
]
ASF GitHub Bot commented on FLINK-6196:
---------------------------------------
Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/3623#discussion_r109929426
--- Diff:
flink-libraries/flink-table/src/main/scala/org/apache/flink/table/functions/utils/TableSqlFunction.scala
---
@@ -53,22 +54,9 @@ class TableSqlFunction(
paramTypes,
functionImpl) {
- /**
- * Get the user-defined table function.
- */
- def getTableFunction = udtf
-
- /**
- * Get the type information of the table returned by the table function.
- */
- def getRowTypeInfo = rowTypeInfo
-
- /**
- * Get additional mapping information if the returned table type is a
POJO
- * (POJO types have no deterministic field order).
- */
- def getPojoFieldMapping = functionImpl.fieldIndexes
--- End diff --
are POJOs still supported?
> Support dynamic schema in Table Function
> ----------------------------------------
>
> Key: FLINK-6196
> URL: https://issues.apache.org/jira/browse/FLINK-6196
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Zhuoluo Yang
> Assignee: Zhuoluo Yang
>
> In many of our use cases. We have to decide the schema of a UDTF at the run
> time. For example. udtf('c1, c2, c3') will generate three columns for a
> lateral view.
> Most systems such as calcite and hive support this feature. However, the
> current implementation of flink didn't implement the feature correctly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
