[SPARK-52934][PYTHON] Allow yielding scalar values with Arrow-optimized Python UDTF #51640
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.
What changes were proposed in this pull request?
Allows yielding scalar values with Arrow-optimized Python UDTF.
Also the error class for the case where the number of columns is different from the return schema is fixed.
Why are the changes needed?
There is a behavior difference in Arrow-optimized Python UDTF between legacy and new serialization.
The behavior should be consistent.
Does this PR introduce any user-facing change?
Yes, the new code path allows yielding scalar values.
How was this patch tested?
Updated the related tests.
Was this patch authored or co-authored using generative AI tooling?
No.