[
https://issues.apache.org/jira/browse/SPARK-34111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon updated SPARK-34111:
---------------------------------
Description:
After SPARK-33705, we now happened to have two jars in the release artifact
with Hadoop 3:
{{dev/deps/spark-deps-hadoop-3.2-hive-2.3}}:
{code}
...
jakarta.servlet-api/4.0.3//jakarta.servlet-api-4.0.3.jar
...
javax.servlet-api/3.1.0//javax.servlet-api-3.1.0.jar
...
{code}
It can potentially cause an issue, and we should better remove
{{javax.servlet-api-3.1.0.jar}} which is apparently only required for YARN
tests.
was:
After SPARK-33705, we now happened to have two jars in the release artifact
with Hadoop 3:
{{dev/deps/spark-deps-hadoop-3.2-hive-2.3}}:
{code}
...
jakarta.servlet-api/4.0.3//jakarta.servlet-api-4.0.3.jar
...
javax.servlet-api/3.1.0//javax.servlet-api-3.1.0.jar
...
{code}
It can potentially cause an issue, and we should better remove
{{javax.servlet-api-3.1.0.jar
}} which is apparently only required for YARN tests.
> Deconflict the jars jakarta.servlet-api-4.0.3.jar and
> javax.servlet-api-3.1.0.jar
> ---------------------------------------------------------------------------------
>
> Key: SPARK-34111
> URL: https://issues.apache.org/jira/browse/SPARK-34111
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 3.1.0
> Reporter: Hyukjin Kwon
> Priority: Blocker
>
> After SPARK-33705, we now happened to have two jars in the release artifact
> with Hadoop 3:
> {{dev/deps/spark-deps-hadoop-3.2-hive-2.3}}:
> {code}
> ...
> jakarta.servlet-api/4.0.3//jakarta.servlet-api-4.0.3.jar
> ...
> javax.servlet-api/3.1.0//javax.servlet-api-3.1.0.jar
> ...
> {code}
> It can potentially cause an issue, and we should better remove
> {{javax.servlet-api-3.1.0.jar}} which is apparently only required for YARN
> tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
