[
https://issues.apache.org/jira/browse/HADOOP-18303?focusedWorklogId=784332&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-784332
]
ASF GitHub Bot logged work on HADOOP-18303:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jun/22 18:47
Start Date: 23/Jun/22 18:47
Worklog Time Spent: 10m
Work Description: sunchao commented on PR #4461:
URL: https://github.com/apache/hadoop/pull/4461#issuecomment-1164752328
> @sunchao It doesn't, that is what I was saying, even if we sort the
shading issue, the Tez issue is gonna stay because it doesn't use the shaded
Jar and gets both these jars in classpath and things mess up.
I see. This looks like a separate issue from this PR, is that correct? is
this because of https://issues.apache.org/jira/browse/HADOOP-18033?
The issue seems tricky though. I wonder if we can shade jersey 2 in
`hadoop-thirdparty` and then update Hadoop to use that.
Issue Time Tracking
-------------------
Worklog Id: (was: 784332)
Time Spent: 2h 20m (was: 2h 10m)
> Remove shading exclusion of javax.ws.rs-api from hadoop-client-runtime
> ----------------------------------------------------------------------
>
> Key: HADOOP-18303
> URL: https://issues.apache.org/jira/browse/HADOOP-18303
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Critical
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> As part of HADOOP-18033, we have excluded shading of javax.ws.rs-api from
> both hadoop-client-runtime and hadoop-client-minicluster. This has caused
> issues for downstreamers e.g.
> [https://github.com/apache/incubator-kyuubi/issues/2904], more discussions.
> We should put the shading back in hadoop-client-runtime to fix CNFE issues
> for downstreamers.
> cc [~ayushsaxena] [~pan3793]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
