[ 
https://issues.apache.org/jira/browse/PHOENIX-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793618#comment-17793618
 ] 

Istvan Toth commented on PHOENIX-7141:
--------------------------------------

Surprisingly, 5.1 has almost as much unshaded stuff as master.

Unshaded packages in 5.1 HEAD:
* com.beust: coming from omid, see OMID-267
* io.netty (4.1): coming from zk and omid-transaction-client
* javax.inject: coming form omid, I  think we can safely relocate it
* mozilla:  ????
* tables: we are shading this in the clients, I see no reason not do the same 
in server
* org.checkerframework: Seems to be an interaction between checker-qual coming 
via hadoop-common -> guava, and guava
* org.codehaus.mojo.animalsniffer: TBD
* org.yaml.snakeyaml: TBD
* org.apache.commons.configuration: TBD
* org.apache.commons.configuration2: TBD
* org.apache.commons.csv: TBD
* org.apache.curator: TBD
* org.apache.statemachine: TBD


I was hoping that 5.1 has less problem, but this is not the case.

> hbase-server shading problems
> -----------------------------
>
>                 Key: PHOENIX-7141
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7141
>             Project: Phoenix
>          Issue Type: Bug
>          Components: core
>            Reporter: Istvan Toth
>            Priority: Blocker
>
> HBase-server is different from the rest of the shaded artifacts in that it it 
> doesn't shade packages by default.
> As new dependencies were added to Phoenix, we were left with an hbase-server 
> jar which includes unshaded libraries which potentially conflict with the 
> hbase server classpath.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to