[
https://issues.apache.org/jira/browse/FLINK-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974380#comment-15974380
]
ASF GitHub Bot commented on FLINK-6196:
---------------------------------------
Github user clarkyzl commented on a diff in the pull request:
https://github.com/apache/flink/pull/3623#discussion_r112156728
--- Diff:
flink-libraries/flink-table/src/main/scala/org/apache/flink/table/plan/schema/DeferredTypeFlinkTableFunction.scala
---
@@ -40,6 +43,10 @@ class DeferredTypeFlinkTableFunction(
val implicitResultType: TypeInformation[_])
extends FlinkTableFunction(tableFunction, evalMethod) {
+ val paramTypeInfos = evalMethod.getParameterTypes.map { paramType =>
+ TypeExtractor.getForClass(paramType)
--- End diff --
I think signature types of the `eval()` method will be better. First, It
will make them no differences in both situations. I think I'd like to try to
do convert the first case to the signatures of the `eval()` method. It will
make it easier to identify which method is called.
> 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)
