You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or challenge?
The changes in #10651 lead to a change in the error messages given when a function is called without any arguments. I think it can be made a little clearer to the user what actually went wrong.
The current error message in main:
"Error during planning: Error during planning: [data_types_with_aggregate_udf] Coercion from [] to the signature VariadicAny failed. and No function matches the given name and argument types 'selector_last()'. You might need to add explicit type casts.\n\tCandidate functions:\n\tselector_last(Any, .., Any)"
Describe the solution you'd like
An error that displays to the user that they called a function that requires arguments without providing any. One example could be:
"Error during planning: Error during planning: SUM does not support zero arguments. No function matches the given name and argument types 'SUM()'. You might need to add explicit type casts.\n\tCandidate functions:\n\tSUM(UserDefine
d)"
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem or challenge?
The changes in #10651 lead to a change in the error messages given when a function is called without any arguments. I think it can be made a little clearer to the user what actually went wrong.
The current error message in main:
Describe the solution you'd like
An error that displays to the user that they called a function that requires arguments without providing any. One example could be:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: