You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2019/09/25 04:03:00 UTC

[jira] [Resolved] (CALCITE-3323) Handle arbitrary/unknown functions that have ordinary syntax

     [ https://issues.apache.org/jira/browse/CALCITE-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-3323.
----------------------------------
    Fix Version/s: 1.22.0
       Resolution: Fixed

Fixed in [ed692fd4|https://github.com/apache/calcite/commit/ed692fd4f2f00261348ecac779cb1a6d544d052e]; thanks for the PR, [~fib-seq]!

> Handle arbitrary/unknown functions that have ordinary syntax
> ------------------------------------------------------------
>
>                 Key: CALCITE-3323
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3323
>             Project: Calcite
>          Issue Type: New Feature
>            Reporter: Ryan Fu
>            Priority: Major
>             Fix For: 1.22.0
>
>
> Add a strategy where if a function has ordinary function syntax and we don't recognize it we assume that it can take any argument types and returns a result of unknown type.
> We will still need to change the parser to handle functions with non-standard syntax (e.g. DATEADD). And it's a good idea to explicitly add commonly used non-standard functions (e.g. MD5, CONCAT).”
> [19/Sept/2019] Functions have to have ordinary function syntax [e.g. foo(arg0, ...)]. Current implementation idea is to:
>  * Create a known/unknown flag for use within the validator
>  * Create a more permissive SqlUnresolvedFunction to be passed through validator
>  ** Allow OperandTypes to be variadic



--
This message was sent by Atlassian Jira
(v8.3.4#803005)