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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.32.0
• Component/s: core
• Assignee: Unassigned
• Reporter: Tuomas Kiviaho
• Created: 03/Nov/22 17:35
• Updated: 12/Nov/22 06:38

Description

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.

Issue Links

• is related to: CALCITE-941 Named, optional and DEFAULT arguments to function calls