[SPARK-45159][PYTHON] Handle named arguments only when necessary #42915
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HyukjinKwon
approved these changes
Sep 15, 2023
|
Merged to master. |
| check_return_value(res) | ||
| yield verify_result(pd.DataFrame(res)), arrow_return_type | ||
|
|
||
| return evaluate | ||
|
|
||
| eval = wrap_arrow_udtf(getattr(udtf, "eval"), return_type) | ||
| eval_func_kwargs_support, args_kwargs_offsets = wrap_kwargs_support( |
There was a problem hiding this comment.
It would be really good to comment here on why we need to wrap the kwargs separately. This can provide valuable context for those who work on this code in the future. :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Handles named arguments only when necessary.
Why are the changes needed?
Constructing
kwargsasdictcould be expensive. It should be done only when necessary.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.
Was this patch authored or co-authored using generative AI tooling?
No.