[
https://issues.apache.org/jira/browse/RANGER-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800979#comment-16800979
]
Bolke de Bruin commented on RANGER-2370:
----------------------------------------
[~madhan.neethiraj] We still see issues that due to e.g. Guava being loaded by
Presto on the classpath earlier than the ranger-plugin-classloader is
instantiated it sill has conflicting libraries. Is the pattern with other
implementations to load the classloader somehow earlier and thus making the
presto patch more invasive? Do you have an example where that is done?
> 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)
