[ 
https://issues.apache.org/jira/browse/HADOOP-18303?focusedWorklogId=783292&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-783292
 ]

ASF GitHub Bot logged work on HADOOP-18303:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Jun/22 09:44
            Start Date: 21/Jun/22 09:44
    Worklog Time Spent: 10m 
      Work Description: steveloughran commented on PR #4461:
URL: https://github.com/apache/hadoop/pull/4461#issuecomment-1161514464

   i wouldn't trust the ordering of the merge. could one jar be excluded 
explicitly.
   
   I'm getting really confused now. Before this PR, conflicting imports were 
both being shaded. Now they are being merged in unshaded and the issue is 
*which ones not to shade?*




Issue Time Tracking
-------------------

    Worklog Id:     (was: 783292)
    Time Spent: 1h  (was: 50m)

> 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: 1h
>  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]

Reply via email to