I'm good with shading it internally in apex-engine for now until there is
an actual need in a real use case. Thanks!

David

On Fri, Jul 8, 2016 at 4:42 PM, Pramod Immaneni <[email protected]>
wrote:

> Good question. Even though it would be useful for somebody wanting to use
> SPNEGO in their operator for example I don't see any immediate use. We can
> just go with it being internal and create a separate artifact in future if
> need arises. What do you think?
>
> Thanks
>
> On Fri, Jul 8, 2016 at 11:40 AM, David Yan <[email protected]> wrote:
>
> > +1 for the change. This would fix dependency conflicts between httpclient
> > 4.2.5 and 4.3.5.
> > I think the question is whether we should publish a separate shaded
> > artifact (like we did for ning-ahc) for the shaded httpclient 4.3.5, or
> > just shading it internally in apex-engine. The former allows application
> > and operator developers to use the shaded artifact and the latter hides
> it
> > completely.
> >
> > Davod
> >
> > On Fri, Jul 8, 2016 at 11:31 AM, Pramod Immaneni <[email protected]
> >
> > wrote:
> >
> > > Forgot to add that 4.3.5 is a later version that what newer versions of
> > > hadoop are using (4.2.5) and we need it for kerberos SPNEGO security
> > > related functionality.
> > >
> > > Thanks
> > >
> > > On Fri, Jul 8, 2016 at 11:28 AM, Pramod Immaneni <
> [email protected]
> > >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > We have seen an issue with different versions of
> > > > org.apache.httpcomponents:httpclient jar getting included in
> classpath
> > > when
> > > > apps are launched on newer versions of Hadoop. This is because we
> have
> > an
> > > > explicit dependency in Apex to version 4.3.5, the version of hadoop
> we
> > > > build against (2.2 for backward compatibility) does not have a
> > dependency
> > > > to this artifact but newer versions of hadoop have this dependency.
> To
> > > get
> > > > around this problem we are thinking of shading this dependency
> > internally
> > > > in apex. Any other ideas or suggestions?
> > > >
> > > > Thanks
> > > >
> > >
> >
>

Reply via email to