[
https://issues.apache.org/jira/browse/CALCITE-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043155#comment-16043155
]
Julian Hyde commented on CALCITE-1833:
--------------------------------------
Can you explain this in terms that would make sense to the end user? Does
"Allow user-defined aggregate function to have more than one parameter" capture
it?
> SqlAggFunction need new constructor to set paramTypes not be null for support
> multiple parameters for udaf
> ----------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-1833
> URL: https://issues.apache.org/jira/browse/CALCITE-1833
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.12.0
> Reporter: yuemeng
> Assignee: Julian Hyde
> Priority: Blocker
>
> If a class(A) implement interface of AggregateFunction,that instance of class
> will be transformed to instance of SqlUserDefinedAggFunction by call toOp
> method in CalciteCatalogReader.
> when construct the SqlUserDefinedAggFunction instance will set paramTypes to
> null for super class sqlFunction indirectly.
> The problem is:
> we will get SqlUserDefinedAggFunction paramTypes to sql validatefilte,but it
> will be filter nothing
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
