[
https://issues.apache.org/jira/browse/PHOENIX-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603563#comment-15603563
]
Eric Lomore commented on PHOENIX-3355:
--------------------------------------
For 2, I'll proceed with that then. I was just concerned that iterating could
become expensive when we have to manually check for i =1 .... x at some point
terminating even if we haven't found the function.
For 3, I don't think there's a definite return type. An example would be
COALESCE where it depends on the input type. While we should have the return
type during parse time, I don't see that data contained within the
builtinfunctioninfo or any other function classes. It seems like it's handled
at runtime.
> Register Phoenix built-in functions as Calcite functions
> --------------------------------------------------------
>
> Key: PHOENIX-3355
> URL: https://issues.apache.org/jira/browse/PHOENIX-3355
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Eric Lomore
> Labels: calcite
> Attachments: PHOENIX-3355.wip
>
>
> We should register all Phoenix built-in functions that don't exist in Calcite.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
