[
https://issues.apache.org/jira/browse/HADOOP-18033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555804#comment-17555804
]
Viraj Jasani commented on HADOOP-18033:
---------------------------------------
[~ayushtkn] Thanks for posting your findings, just had a high level glance at
the above failure stacktrace in Tez.
{quote}at
org.apache.tez.dag.history.ats.acls.ATSHistoryACLPolicyManager.createTimelineDomain(ATSHistoryACLPolicyManager.java:127)
{quote}
For this one, is it be convenient to include javax.ws.rs-api in
[https://github.com/apache/tez/blob/master/tez-plugins/tez-yarn-timeline-history-with-acls/pom.xml]
? Or does that also conflict with jsr311-api?
I understand the pain with minor release upgrade when it has to deal with such
issues. FWIW, although Hadoop 3.3 could revert this for 3.3.4 release but from
security viewpoint, staying up with latest Jackson2 is also in good favour of
3.3 release line, given that 3.3 is the latest release line. Let me also check
if something can be done in the meantime. (As you already noticed, the problem
here is that with shading, we get multiple duplicate class clashes for
javax.ws.rs dependencies and hence we have no choice but to remove it from
shading)
> Upgrade fasterxml Jackson to 2.13.0
> -----------------------------------
>
> Key: HADOOP-18033
> URL: https://issues.apache.org/jira/browse/HADOOP-18033
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Reporter: Akira Ajisaka
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.2
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> Spark 3.2.0 depends on Jackson 2.12.3. Let's upgrade to 2.12.5 (2.12.x latest
> as of now) or upper.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
