[
https://issues.apache.org/jira/browse/FLINK-39915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-39915:
-----------------------------------
Labels: pull-request-available (was: )
> Throw a clear validation error when mixing positional and named function
> arguments
> ----------------------------------------------------------------------------------
>
> Key: FLINK-39915
> URL: https://issues.apache.org/jira/browse/FLINK-39915
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Affects Versions: 2.3.0
> Reporter: Gustavo de Morais
> Assignee: Gustavo de Morais
> Priority: Critical
> Labels: pull-request-available
>
> Calling a function with a mix of positional and named arguments - e.g.
> `f(TABLE t, op => DESCRIPTOR(x))` - fails during validation with a generic
> calcite assertion error instead of a helpful message.
> Root cause is in Calcite's operand permutation: once any argument is named it
> assumes all are, and a positional argument trips an assertion.
> Detect the mix early in `FlinkCalciteSqlValidator` and throw a
> `ValidationException` telling the user to use either all positional or all
> named arguments. Affects every function with named-argument support (process
> table functions, table functions, scalar functions).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
