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-33216][INFRA][PYTHON][2.4] Set upper bound of Pandas version in GitHub Actions #30127
Conversation
@HyukjinKwon How do you think about this? |
Kubernetes integration test starting |
@HyukjinKwon . I'll close this PR in favor of SPARK-30777. |
Please recover branch-2.4~ Thank you in advance. |
Ohh okay got it. There are more tests being failed. |
Some of them require Arrow dep upgrade in pom which isn't possible. I thought I fixed it by setting upper bound of PyArrow. Hm, let me fix it by the same approach proposed here. |
Kubernetes integration test status success |
I discussed offline with @dongjoon-hyun. It requires to port at least two PRs 07a9885 and 16990f9 + Arrow dependency upgrade in POM side which is not possible. Setting the upper bound looks correct approach. It was my bad that I thought it just needs one backport. |
Thank you for investigating all the stuff and guiding this, @HyukjinKwon ! |
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.
LGTM: it can just set to whichever pandas version that makes the build in branch-2.4
Kubernetes integration test starting |
@dongjoon-hyun, I will open another PR with picking your commits - seems it fails. |
Kubernetes integration test status success |
Test build #130121 has finished for PR 30127 at commit
|
Test build #130120 has finished for PR 30127 at commit
|
Test build #130122 has finished for PR 30127 at commit
|
What changes were proposed in this pull request?
This PR aims to pin
Pandas
version up to1.1.0
released onJuly 28
.Why are the changes needed?
branch-2.4
GitHub Action was broken sinceAug 26
due to Pandas API incompatibility.The following is just one example.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the GitHub Action.