-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-35959][BUILD][test-maven][test-hadoop3.2][test-java11] Add a new Maven profile "no-shaded-hadoop-client" for Hadoop versions older than 3.2.2/3.3.1 #33160
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 |
|
Kubernetes integration test status success |
|
Test build #140469 has finished for PR 33160 at commit
|
|
Kubernetes integration test unable to build dist. exiting with code: 1 |
|
Test build #140487 has finished for PR 33160 at commit
|
dongjoon-hyun
left a comment
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.
Hi, @sunchao .
To verify via CI, could you make the profile active by default? After testing, we should remove it.
|
FYI, if you enable it by default, the dependency files are required to be updated accordingly. |
Thanks @dongjoon-hyun . Will do. |
|
Test build #140531 has finished for PR 33160 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Kubernetes integration test unable to build dist. exiting with code: 1 |
|
For Hadoop 2 build, I noticed that GitHub Action job used For the other part, it looks good to me. After one hour, if GitHub Action passed, let's revert |
|
Test build #140537 has finished for PR 33160 at commit
|
Hmm for some reason it is still using Hadoop 3.3.1 classes which is only compatible with jetty 9.4+. Let me check why it happens. |
|
Let me check the PR builder. |
|
So, |
|
Yeah, but somehow it references Hadoop 3.3.1 class like |
|
It seems to be a Spark bug which works only at maven and not on sbt. |
|
In this case, we used to use |
|
Let me try. |
|
Retest this please |
|
@dongjoon-hyun ahh I think you are right! seems sbt doesn't parse the |
|
Test build #140560 has finished for PR 33160 at commit
|
|
Kubernetes integration test status failure |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #140714 has finished for PR 33160 at commit
|
|
Kubernetes integration test starting |
|
Test build #140721 has finished for PR 33160 at commit
|
|
Kubernetes integration test status failure |
|
It seems Spark can't use non-shaded Hadoop 3.3.1 client as it is because of |
3ffecf8 to
4bf4533
Compare
|
Kubernetes integration test unable to build dist. exiting with code: 1 |
|
Test build #142369 has finished for PR 33160 at commit
|
could move hadoop 3.3.2 to the same jetty version; if we get that out then things will briefly be in sync |
|
@steveloughran yes we can, this is only an issue when Spark uses the non-shaded client though so I think it's OK, since it's better to just use the shaded client. |
|
Kubernetes integration test unable to build dist. exiting with code: 1 |
|
you got any plans to update that hadoop jetty version alongside this? |
|
@steveloughran you mean upgrade jetty version in Hadoop? yea I can check, but anyways Spark is not blocked by the jetty thing. |
|
We're closing this PR because it hasn't been updated in a while. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
What changes were proposed in this pull request?
Add a new Maven profile
no-shaded-hadoop-clientthat, when activated, switches to non-shaded Hadoop client (e.g.,hadoop-client,hadoop-yarn-client, etc).Why are the changes needed?
Currently Spark uses Hadoop shaded client by default. However, if Spark users want to build Spark with older version of Hadoop, such as 3.1.x, the shaded client cannot be used as it currently it only support Hadoop 3.2.2+ and 3.3.1+). Therefore, this proposes to offer a new Maven profile "no-shaded-hadoop-client" for this use case.
Does this PR introduce any user-facing change?
Yes, now users can choose to build Apache Spark with non-shaded Hadoop client, e.g.:
How was this patch tested?
Existing tests.