[SPARK-50126][PYTHON][CONNECT][3.5] PySpark expr() (expression) SQL Function returns None in Spark Connect #49755
+14
−1
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
…unction returns None in Spark Connect Cherry-pick apache#46583 to branch-3.5 Original JIRA: SPARK-48276
|
@zhengruifeng : Tagging you for review as the original author of this change. |
|
Build github workflows failing above due to deprecation of v3 actions/upload-artifact. |
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.
Cherry-pick #46583 to branch-3.5
Original JIRA: SPARK-48276
What changes were proposed in this pull request?
Original PR proposed these changes:
__repr__method forSQLExpressionlit(None): None -> NULLto be more consistent with the Spark ClassicI had to make very minor modifications to fix unclean cherry-pick:
Why are the changes needed?
Spark Connectconfiguration, calls topyspark.sql.functions.exprincorrectly returnColumn<None>instead of the expected expression. This change addresses the issue to ensure proper expression resolution in Spark Connect mode.__repr__method.Does this PR introduce any user-facing change?
Yes, this PR ensures that
pyspark.sql.functions.exprcorrectly resolves expressions in Spark Connect mode. Previously, it returnedColumn<None>, but now it behaves correctly.How was this patch tested?
Manually tested. Also original PR added a UT.
Was this patch authored or co-authored using generative AI tooling?
No.