I also believe Hadoop have some optional classloader to isolate hadoop
internal classpath from application classpath, like that guy:
https://hadoop.apache.org/docs/r2.7.2/api/org/apache/hadoop/util/ApplicationClassLoader.html

Laurent

On Wed, Apr 6, 2016 at 12:34 PM, Hanifi Gunes <[email protected]> wrote:

> Shading might be an option here.
>
> Thanks.
> -Hanifi
>
> 1: https://maven.apache.org/plugins/maven-shade-plugin/
>
>
> On Thu, Mar 31, 2016 at 6:04 PM, Paul Rogers <[email protected]> wrote:
>
> > Hi All,
> >
> > Here’s an obscure question for the expert developers…
> >
> > We’re developing the YARN Application Master (AM) for Drill. We’d like to
> > monitor Drill’s ZooKeeper (ZK) Drill-bit registrations. Since the ZK
> > entries are in Protobuf format, and Drill already has classes do to the
> > monitoring, the logical solution is just to use the Drill code in the AM.
> >
> > The problem is, the dependencies (such as Guava version) for Drill differ
> > from those of Hadoop. Simply including Drill and YARN libraries in the
> same
> > build trigger runtime failures due to Guava version incompatibilities.
> >
> > One solution is to create a custom class loader for the Drill classes,
> but
> > that introduces a different set of complexities.
> >
> > Suggestions?
> >
> > Thanks,
> >
> > - Paul
> >
> >
>

Reply via email to