-
Notifications
You must be signed in to change notification settings - Fork 28.6k
[SPARK-32381][CORE][FOLLOWUP][test-hadoop2.7] Don't remove SerializableFileStatus and SerializableBlockLocation for Hadoop 2.7 #30447
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
Conversation
Kubernetes integration test starting |
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 pending Jenkins, one minor suggestion re: adding a comment.
Kubernetes integration test status success |
Kubernetes integration test starting |
Kubernetes integration test status failure |
Test build #131432 has finished for PR 30447 at commit
|
Cool the jenkins CI passed and the failure in github CI seems not related. I updated the PR with some comments. |
Test build #131434 has finished for PR 30447 at commit
|
Kubernetes integration test starting |
Kubernetes integration test status failure |
Jenkins retest this please. |
Test build #131442 has finished for PR 30447 at commit
|
Kubernetes integration test starting |
Kubernetes integration test status success |
Test build #131453 has finished for PR 30447 at commit
|
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.
+1, LGTM. Thanks, @sunchao and @holdenk .
This passed at #30447 (comment)
Merged to master to recover Hadoop 2.7 profile.
Thanks @dongjoon-hyun and @holdenk ! |
What changes were proposed in this pull request?
Revert the change in #29959 and don't remove
SerializableFileStatus
andSerializableBlockLocation
.Why are the changes needed?
In Hadoop 2.7
FileStatus
andBlockLocation
are not serializable, so we still need the two wrapper classes.Does this PR introduce any user-facing change?
No
How was this patch tested?
N/A