[
https://issues.apache.org/jira/browse/CALCITE-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953495#comment-17953495
]
Alessandro Solimando commented on CALCITE-7035:
-----------------------------------------------
Thanks [~jensen], I saw the discussion around this change in the PR for
CALCITE-6978, even if not ideal it would be a workaround until we implement
CALCITE-7012.
>From that ticket and [this
>discussion|https://github.com/apache/calcite/pull/4355/files#r2073217842] in
>the PR, it seems that all this is intended, but nobody thought about what
>would happen to functions without implementors/converlet which are supposed to
>be rewritten to something else no matter what.
If we could programmatically identify those functions, we could allow expansion
until CALCITE-7012 gets implemented. If that's not possible, the workaround
proposed by [~jensen] sounds viable to me.
> SQL calls without an implementor or convertlet (NULLIF, YEAR, ...) throw an
> error when having a subquery as parameter
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-7035
> URL: https://issues.apache.org/jira/browse/CALCITE-7035
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.40.0
> Reporter: Aleksey Plekhanov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.40.0
>
>
> After CALCITE-6978 {{SqlCall}}'s with subqueries are not rewritten during
> validation even when {{withCallRewrite(true)}} property is set in the
> configuration.
> Functions like {{NULLIF}}, {{YEAR}}, {{MONTH}}, etc don't have implementor or
> convertlet, so, when used with subqueries, throw an error: Unable to
> implement.
> Examples of problematic queries:
> {noformat}
> select nullif((select max(emps.age) from emps), 0);
> select year(select max(joinedat) from emps);
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
