[
https://issues.apache.org/jira/browse/CALCITE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165344#comment-17165344
]
Rui Wang commented on CALCITE-2569:
-----------------------------------
Yes. That change is in the following "fixup" commit. I missed that one. Thanks
for updating window table functions!
Currently I don't have further comment on whether it is a good idea that return
type is CURSOR meanwhile row type is inferred by another API. From the change
at least it seems offering a unified row type inference cross different types
of table functions.
We can keep the change and see how well it works, especially in the future,
with polynomial table function.
> UDFs that are table functions must implement SqlTableFunction and have CURSOR
> as their return type
> --------------------------------------------------------------------------------------------------
>
> Key: CALCITE-2569
> URL: https://issues.apache.org/jira/browse/CALCITE-2569
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Priority: Major
>
> UDFs that are table functions must implement SqlTableFunction and have CURSOR
> as their return type,
> Validate that table functions are not used in contexts that require scalar
> functions, such as the SELECT clause.
> Change operand type ANY to mean 'scalar expression of any type (but not a
> cursor)', and add operand type IGNORE to mean skip validation - for an
> operand that is not an expression. TABLE is one of the few operators that
> accepts a CURSOR operand.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
