[SPARK-47933][CONNECT][PYTHON][FOLLOW-UP] Avoid referencing _to_seq in pyspark-connect
#46229
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
|
Merged to master. |
HyukjinKwon
added a commit
that referenced
this pull request
Apr 30, 2024
… classes ### What changes were proposed in this pull request? This PR proposes to fix `pyspark-connect` build that is broken by #46155. It is similar with the followups such as #46229 and #46262 but make sure the tests pass within this PR. ### Why are the changes needed? To recover the CI https://github.com/apache/spark/actions/runs/8884003967 ### Does this PR introduce _any_ user-facing change? No, the main change has not been released yet. ### How was this patch tested? CI in my own fork: https://github.com/HyukjinKwon/spark/actions/runs/8889698252/job/24408487227 ### Was this patch authored or co-authored using generative AI tooling? No. Closes #46294 from HyukjinKwon/SPARK-48052. Authored-by: Hyukjin Kwon <gurwls223@apache.org> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
JacobZheng0927
pushed a commit
to JacobZheng0927/spark
that referenced
this pull request
May 11, 2024
…n `pyspark-connect` ### What changes were proposed in this pull request? This PR is a followup of apache#46155 that removes the reference of `_to_seq` that `pyspark-connect` package does not have. ### Why are the changes needed? To recover the CI https://github.com/apache/spark/actions/runs/8821919392/job/24218893631 ### Does this PR introduce _any_ user-facing change? No, the main change has not been released out yet. ### How was this patch tested? Manually tested. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#46229 from HyukjinKwon/SPARK-47933-followuptmp. Authored-by: Hyukjin Kwon <gurwls223@apache.org> Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
JacobZheng0927
pushed a commit
to JacobZheng0927/spark
that referenced
this pull request
May 11, 2024
… classes ### What changes were proposed in this pull request? This PR proposes to fix `pyspark-connect` build that is broken by apache#46155. It is similar with the followups such as apache#46229 and apache#46262 but make sure the tests pass within this PR. ### Why are the changes needed? To recover the CI https://github.com/apache/spark/actions/runs/8884003967 ### Does this PR introduce _any_ user-facing change? No, the main change has not been released yet. ### How was this patch tested? CI in my own fork: https://github.com/HyukjinKwon/spark/actions/runs/8889698252/job/24408487227 ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#46294 from HyukjinKwon/SPARK-48052. Authored-by: Hyukjin Kwon <gurwls223@apache.org> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
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?
This PR is a followup of #46155 that removes the reference of
_to_seqthatpyspark-connectpackage does not have.Why are the changes needed?
To recover the CI https://github.com/apache/spark/actions/runs/8821919392/job/24218893631
Does this PR introduce any user-facing change?
No, the main change has not been released out yet.
How was this patch tested?
Manually tested.
Was this patch authored or co-authored using generative AI tooling?
No.