[
https://issues.apache.org/jira/browse/PHOENIX-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562765#comment-15562765
]
James Taylor commented on PHOENIX-3355:
---------------------------------------
In general, the execution will be handled by Phoenix, but the parsing,
validation, compilation, and planning should be done by Calcite (and the
Phoenix/Calcite integration code). For built-in functions, we'll want to stick
exclusively to using Phoenix built-in functions as otherwise when their
execution is pushed to the server (namely when a function is used in a WHERE
clause), the Calcite-based built-in functions wouldn't work as there's no
mechanism to generate code on the server side.
For DDL statements, can you give an example of one that's not being validated?
Is it when you execute a CREATE VIEW statement? It may be that the validation
occurs in Calcite when the view statement is used rather than when it's
created. [~maryannxue] or [~julianhyde] would know.
> 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
>
> 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)
