[
https://issues.apache.org/jira/browse/RANGER-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801864#comment-16801864
]
Madhan Neethiraj commented on RANGER-2370:
------------------------------------------
[~bolke] - if a library is included in the base component itself, please
exclude it from plugin-impl directory. i.e. if Presto already includes a
version of Guava, plugin-impl directory shouldn't include Guava libraries. I
think shading is a 'shady' practice (which makes it difficult to understand the
libraries used in a deployment) and should be avoided wherever possible.
> Hadoop-common should be shaded in agents-common and agents-audit
> ----------------------------------------------------------------
>
> Key: RANGER-2370
> URL: https://issues.apache.org/jira/browse/RANGER-2370
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
> Affects Versions: 1.2.0
> Reporter: Bolke de Bruin
> Priority: Critical
>
> Hadoop-common pulls in a lot of dependencies, particularly Guava, Jersey that
> are also often used in other projects. Guava and Jersey are particularly
> notorious for being 'tough' dependencies as they are not backwards compatible.
> As 'ranger-plugin-common' and 'ranger-plugins-audit' are to be integrated
> with 3rd party services this poses serious challenges. For example the Presto
> plugin (see linked issue) is currently blocked due to the reliance of Presto
> on Jersey 2, while Hadoop/Ranger use Jersey 1.X.
> An example of how to shade Hadoop Common can be found here:
> [https://github.com/gchq/hadoop-common-shaded/] .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
