Re-support Signature::Any(0)
, and add tests for zero argument udfs
#13871
+58
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Signature::nullary
in 44.0.0 easier / less confusing #13763Rationale for this change
As described on #13763
In version s 43.0.0 and earlier of DataFusion, a
TypeSignature::Any(0)
means your udf could be called with zero arguments:SELECT my_udf();
However in version 44.0.0 you get a very confusing error that says zero arguments are not supported but then gives you a candidate function is the one it just said was not supported:
I believe @jayzhan211 added this error to try and guide people to ensure people used the newly introduced
Signature::Nullary
(see #13763 (comment))What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?