New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-36333][PYTHON] Reuse isnull where the null check is needed #33562
Conversation
cc @xinrong-databricks @HyukjinKwon @itholic |
Test build #141793 has finished for PR 33562 at commit
|
Kubernetes integration test starting |
Kubernetes integration test status success |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Otherwise, LGTM.
I'm not sure #33562 (comment) is necessary, though.
Test build #141857 has finished for PR 33562 at commit
|
Kubernetes integration test starting |
Thanks! merging to master/3.2 |
### What changes were proposed in this pull request? Reuse `IndexOpsMixin.isnull()` where the null check is needed. ### Why are the changes needed? There are some places where we can reuse `IndexOpsMixin.isnull()` instead of directly using Spark `Column`. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Existing tests. Closes #33562 from ueshin/issues/SPARK-36333/reuse_isnull. Authored-by: Takuya UESHIN <ueshin@databricks.com> Signed-off-by: Takuya UESHIN <ueshin@databricks.com> (cherry picked from commit 07ed82b) Signed-off-by: Takuya UESHIN <ueshin@databricks.com>
Kubernetes integration test status success |
What changes were proposed in this pull request?
Reuse
IndexOpsMixin.isnull()
where the null check is needed.Why are the changes needed?
There are some places where we can reuse
IndexOpsMixin.isnull()
instead of directly using SparkColumn
.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.