[
https://issues.apache.org/jira/browse/CALCITE-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202960#comment-17202960
]
Danny Chen commented on CALCITE-4283:
-------------------------------------
Finally i change to not force implement the {{SqlTableFunction}} interface for
the sql operator, because we have already generate the logical rel node, e.g.
the {{LogicalTableFunctionScan}}.
Let the downstream project to have the freedom customize the return type
inference. Not through the param types and param names.
> Do not force implement SqlTableFunction when creating table function scan
> -------------------------------------------------------------------------
>
> Key: CALCITE-4283
> URL: https://issues.apache.org/jira/browse/CALCITE-4283
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.25.0
> Reporter: Danny Chen
> Assignee: Danny Chen
> Priority: Major
> Fix For: 1.26.0
>
>
> Throw a more meaningful error message instead of a AssertionError by the
> explicit type cast.
> {code:java}
> final SqlTableFunction operator = (SqlTableFunction) call.getOperator();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
