You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by Stack <st...@duboce.net> on 2017/04/11 20:03:09 UTC

FYI: HBase looking to shade/hide/remove core libs like netty and guava in hbase2

Projects like Phoenix could run would their own versions of libs thereafter
(but would no longer be able to depend nor transitively include from hbase).

Discussion is ongoing (See "[DISCUSS] More Shading"). Pitch in please if
interested/concerned.

Thanks,
St.Ack

Re: FYI: HBase looking to shade/hide/remove core libs like netty and guava in hbase2

Posted by Josh Elser <el...@apache.org>.

Sergey too. ;)

Will catch up over on dev@hbase. Thanks for making sure we were aware of
this one downstream, Stack.

On Apr 11, 2017 19:53, "James Taylor" <ja...@apache.org> wrote:

> Thanks for the heads-up, Stack. Josh is our resident shading expert -
> hopefully he'll chime in based on his experience/expertise.
>
>     James
>
> On Tue, Apr 11, 2017 at 1:03 PM, Stack <st...@duboce.net> wrote:
>
>> Projects like Phoenix could run would their own versions of libs
>> thereafter
>> (but would no longer be able to depend nor transitively include from
>> hbase).
>>
>> Discussion is ongoing (See "[DISCUSS] More Shading"). Pitch in please if
>> interested/concerned.
>>
>> Thanks,
>> St.Ack
>>
>
>

Re: FYI: HBase looking to shade/hide/remove core libs like netty and guava in hbase2

Posted by James Taylor <ja...@apache.org>.

Thanks for the heads-up, Stack. Josh is our resident shading expert -
hopefully he'll chime in based on his experience/expertise.

    James

On Tue, Apr 11, 2017 at 1:03 PM, Stack <st...@duboce.net> wrote:

> Projects like Phoenix could run would their own versions of libs thereafter
> (but would no longer be able to depend nor transitively include from
> hbase).
>
> Discussion is ongoing (See "[DISCUSS] More Shading"). Pitch in please if
> interested/concerned.
>
> Thanks,
> St.Ack
>