[
https://issues.apache.org/jira/browse/RANGER-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794349#comment-16794349
]
Madhan Neethiraj commented on RANGER-2370:
------------------------------------------
[~bolke] - shim approach used in Ranger plugins (look for projects named as
*plugin-shim) should help in avoiding issues such as library version conflicts.
It basically avoids adding any dependency libraries to component's classpath -
by using a separate class-loader for Ranger plugin and its dependents. Not sure
if Presto plugin follows this approach; if it doesn't, I would suggest to try
this approach first. If the problem exists even after using plugin-shim
approach, can you please add details of the issues seen?
> 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)
