[jira] [Created] (CALCITE-5366) User defined function optional named arguments are required to be present

["Tuomas Kiviaho (Jira)" <ji...@apache.org>]

Tuomas Kiviaho created CALCITE-5366:
---------------------------------------

             Summary: User defined function optional named arguments are required to be present
                 Key: CALCITE-5366
                 URL: https://issues.apache.org/jira/browse/CALCITE-5366
             Project: Calcite
          Issue Type: Bug
          Components: core
    Affects Versions: 1.32.0
            Reporter: Tuomas Kiviaho


In situation where optional parameters are stated before the required ones the {{FamilyOperandTypeChecker#getOperandCountRange}} prohibits leaving these arguments undefined. 

Would it be possible to have  {{getOperandCountRange}} reporting only the number of non-optional parameters in case named parameters are used.

The current behavior might indeed be in line with SQL99 SQL:1999 Part 2 Section 10.4 as the {{SqlUtil#lookupSubjectRoutines}} states, but the current behavior kind of beats the flexibility that named parameters provide.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)