DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Stack <st...@duboce.net>]

Taking a sounding....

We've talked of moving the hbase-rest and hbase-thrift modules out of core
over to hbase-connectors project [2, 3]. The connectors project [1] was
meant for the likes of REST and thrift. I'm thinking of trying to do the
move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
release from hbase-connectors as part of this effort and would make sure it
works w/ 2.3.0.

Thank you,
S


1. https://github.com/apache/hbase-connectors
2. https://issues.apache.org/jira/browse/HBASE-20999
3. https://issues.apache.org/jira/browse/HBASE-20998

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Esteban Gutierrez <es...@cloudera.com.INVALID>]

+1

But it would be great if we can deprecate their presence of those modules
first in 2.3

thanks,
esteban.

--
Cloudera, Inc.



On Mon, Apr 27, 2020 at 11:44 AM Josh Elser <el...@apache.org> wrote:

> +1 to the idea, -0 to the implied execution
>
> I agree hbase-connectors is a better place for REST and thrift, long term.
>
> My concern is that I read this thread as suggesting:
>
> 1. Remove rest/thrift from 2.3
> 1a. Proceed with 2.3.0 rc's
> 2. Add rest/thrift to hbase-connectors
> ...
> n. Release hbase-connectors
>
> I'm not a fan of removing anything which was previously there until
> there is are new releases and documentation to tell me how to do it. I'm
> still trying to help dig out another project who did the 'remove and
> then migrate" and left a pile of busted.
>
> If that's not what you were suggesting, let me shirk back into the
> shadows ;)
>
> On 4/25/20 7:44 PM, Stack wrote:
> > On Fri, Apr 24, 2020 at 10:06 PM Sean Busbey<bu...@apache.org>  wrote:
> >
> >> By "works with it" do you mean has documented steps to work with it or
> do
> >> you mean that the convenience binary that ships for 2.3.0 will have the
> >> same deployment model as prior 2.y releases where I can run those
> services
> >> directly from the download?
> >>
> >>
> > Former. Not the latter. They would no-longer be part of the hbase-2.3.x
> > distribution.
> > S
> >
> >
> >
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Esteban Gutierrez <es...@cloudera.com.INVALID>]

+1

But it would be great if we can deprecate their presence of those modules
first in 2.3

thanks,
esteban.

--
Cloudera, Inc.



On Mon, Apr 27, 2020 at 11:44 AM Josh Elser <el...@apache.org> wrote:

> +1 to the idea, -0 to the implied execution
>
> I agree hbase-connectors is a better place for REST and thrift, long term.
>
> My concern is that I read this thread as suggesting:
>
> 1. Remove rest/thrift from 2.3
> 1a. Proceed with 2.3.0 rc's
> 2. Add rest/thrift to hbase-connectors
> ...
> n. Release hbase-connectors
>
> I'm not a fan of removing anything which was previously there until
> there is are new releases and documentation to tell me how to do it. I'm
> still trying to help dig out another project who did the 'remove and
> then migrate" and left a pile of busted.
>
> If that's not what you were suggesting, let me shirk back into the
> shadows ;)
>
> On 4/25/20 7:44 PM, Stack wrote:
> > On Fri, Apr 24, 2020 at 10:06 PM Sean Busbey<bu...@apache.org>  wrote:
> >
> >> By "works with it" do you mean has documented steps to work with it or
> do
> >> you mean that the convenience binary that ships for 2.3.0 will have the
> >> same deployment model as prior 2.y releases where I can run those
> services
> >> directly from the download?
> >>
> >>
> > Former. Not the latter. They would no-longer be part of the hbase-2.3.x
> > distribution.
> > S
> >
> >
> >
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

["张铎 (Duo Zhang)" <pa...@gmail.com>]

I think we only need to depend on hbase-client for hbase-rest and
hbase-thrift? No?

Sean Busbey <bu...@apache.org> 于2020年4月28日周二 下午1:44写道：

> Can't we adjust the REST server to not need YARN?
>
> On Mon, Apr 27, 2020 at 5:21 PM Josh Elser <el...@apache.org> wrote:
>
> > I'd think we'd want to approach that the other way around. Shade what
> > Jersey we need for REST, and (continue to) let Hadoop run wild.
> >
> > Locking ourselves to specific upstream YARN jars worries me.
> >
> > On 4/27/20 5:05 PM, Nick Dimiduk wrote:
> > > I suppose an alternative is to provide a shaded version of the YARN
> jars
> > > needed by hbase-rest in hbase-thirdparty. We'd need these for both
> > hadoop2
> > > and hadoop3, to pull them in via profile, and to exclude the originals
> > > wherever they appear as transitive deps (though they shouldn't, right?)
> > >
> > > On Mon, Apr 27, 2020 at 11:24 AM Josh Elser <el...@apache.org> wrote:
> > >
> > >>
> > >>
> > >> On 4/27/20 1:52 PM, Nick Dimiduk wrote:
> > >>> On Mon, Apr 27, 2020 at 10:11 Stack<st...@duboce.net>  wrote:
> > >>>
> > >>>> On Mon, Apr 27, 2020 at 9:44 AM Josh Elser<el...@apache.org>
> wrote:
> > >>>>
> > >>>>> +1 to the idea, -0 to the implied execution
> > >>>>>
> > >>>>> I agree hbase-connectors is a better place for REST and thrift,
> long
> > >>>> term.
> > >>>>> My concern is that I read this thread as suggesting:
> > >>>>>
> > >>>>> 1. Remove rest/thrift from 2.3
> > >>>>> 1a. Proceed with 2.3.0 rc's
> > >>>>> 2. Add rest/thrift to hbase-connectors
> > >>>>> ...
> > >>>>> n. Release hbase-connectors
> > >>>>>
> > >>>>> I'm not a fan of removing anything which was previously there until
> > >>>>> there is are new releases and documentation to tell me how to do
> it.
> > >> I'm
> > >>>>> still trying to help dig out another project who did the 'remove
> and
> > >>>>> then migrate" and left a pile of busted.
> > >>>>>
> > >>>>> If that's not what you were suggesting, let me shirk back into the
> > >>>>> shadows;)
> > >>>>>
> > >>>>
> > >>>> Ha ha. Not what I was suggesting but that could for sure happen.
> > >>>>
> > >>>> S
> > >>>>
> > >>>> P.S. I'm having trouble w/ REST jersey1 vs jersey2 vs Hadoop3
> > transitive
> > >>>> includes++. Thrift has sporadic test failures that seem inherent to
> > >> thrift
> > >>>> rather of our manufacture. The discussion here was provoked by a
> > >> daydream
> > >>>> that bringing forward this inevitable migration of REST+thrift would
> > >>>> 'solve' my immediate pain. Wasn't giving too much mind to the amount
> > of
> > >>>> work needed on the other side.
> > >>>
> > >>> I’m not clear on how moving the module out will resolve the class
> path
> > >>> issues. Whether it’s built from the main repo or from the side repo,
> > >> yarn’s
> > >>> transitive hull is still present...
> > >>>
> > >>
> > >> Yeah, understandable :)
> > >>
> > >> I think working with "something" for REST/Thrift in connectors (punt
> on
> > >> H3 to start?) is reasonable. You shouldn't be stuck with the baggage
> of
> > >> Jersey dependencies if that's not the problem you're trying to solve.
> > >>
> > >
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Sean Busbey <bu...@apache.org>]

Can't we adjust the REST server to not need YARN?

On Mon, Apr 27, 2020 at 5:21 PM Josh Elser <el...@apache.org> wrote:

> I'd think we'd want to approach that the other way around. Shade what
> Jersey we need for REST, and (continue to) let Hadoop run wild.
>
> Locking ourselves to specific upstream YARN jars worries me.
>
> On 4/27/20 5:05 PM, Nick Dimiduk wrote:
> > I suppose an alternative is to provide a shaded version of the YARN jars
> > needed by hbase-rest in hbase-thirdparty. We'd need these for both
> hadoop2
> > and hadoop3, to pull them in via profile, and to exclude the originals
> > wherever they appear as transitive deps (though they shouldn't, right?)
> >
> > On Mon, Apr 27, 2020 at 11:24 AM Josh Elser <el...@apache.org> wrote:
> >
> >>
> >>
> >> On 4/27/20 1:52 PM, Nick Dimiduk wrote:
> >>> On Mon, Apr 27, 2020 at 10:11 Stack<st...@duboce.net>  wrote:
> >>>
> >>>> On Mon, Apr 27, 2020 at 9:44 AM Josh Elser<el...@apache.org>  wrote:
> >>>>
> >>>>> +1 to the idea, -0 to the implied execution
> >>>>>
> >>>>> I agree hbase-connectors is a better place for REST and thrift, long
> >>>> term.
> >>>>> My concern is that I read this thread as suggesting:
> >>>>>
> >>>>> 1. Remove rest/thrift from 2.3
> >>>>> 1a. Proceed with 2.3.0 rc's
> >>>>> 2. Add rest/thrift to hbase-connectors
> >>>>> ...
> >>>>> n. Release hbase-connectors
> >>>>>
> >>>>> I'm not a fan of removing anything which was previously there until
> >>>>> there is are new releases and documentation to tell me how to do it.
> >> I'm
> >>>>> still trying to help dig out another project who did the 'remove and
> >>>>> then migrate" and left a pile of busted.
> >>>>>
> >>>>> If that's not what you were suggesting, let me shirk back into the
> >>>>> shadows;)
> >>>>>
> >>>>
> >>>> Ha ha. Not what I was suggesting but that could for sure happen.
> >>>>
> >>>> S
> >>>>
> >>>> P.S. I'm having trouble w/ REST jersey1 vs jersey2 vs Hadoop3
> transitive
> >>>> includes++. Thrift has sporadic test failures that seem inherent to
> >> thrift
> >>>> rather of our manufacture. The discussion here was provoked by a
> >> daydream
> >>>> that bringing forward this inevitable migration of REST+thrift would
> >>>> 'solve' my immediate pain. Wasn't giving too much mind to the amount
> of
> >>>> work needed on the other side.
> >>>
> >>> I’m not clear on how moving the module out will resolve the class path
> >>> issues. Whether it’s built from the main repo or from the side repo,
> >> yarn’s
> >>> transitive hull is still present...
> >>>
> >>
> >> Yeah, understandable :)
> >>
> >> I think working with "something" for REST/Thrift in connectors (punt on
> >> H3 to start?) is reasonable. You shouldn't be stuck with the baggage of
> >> Jersey dependencies if that's not the problem you're trying to solve.
> >>
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Josh Elser <el...@apache.org>]

I'd think we'd want to approach that the other way around. Shade what 
Jersey we need for REST, and (continue to) let Hadoop run wild.

Locking ourselves to specific upstream YARN jars worries me.

On 4/27/20 5:05 PM, Nick Dimiduk wrote:
> I suppose an alternative is to provide a shaded version of the YARN jars
> needed by hbase-rest in hbase-thirdparty. We'd need these for both hadoop2
> and hadoop3, to pull them in via profile, and to exclude the originals
> wherever they appear as transitive deps (though they shouldn't, right?)
> 
> On Mon, Apr 27, 2020 at 11:24 AM Josh Elser <el...@apache.org> wrote:
> 
>>
>>
>> On 4/27/20 1:52 PM, Nick Dimiduk wrote:
>>> On Mon, Apr 27, 2020 at 10:11 Stack<st...@duboce.net>  wrote:
>>>
>>>> On Mon, Apr 27, 2020 at 9:44 AM Josh Elser<el...@apache.org>  wrote:
>>>>
>>>>> +1 to the idea, -0 to the implied execution
>>>>>
>>>>> I agree hbase-connectors is a better place for REST and thrift, long
>>>> term.
>>>>> My concern is that I read this thread as suggesting:
>>>>>
>>>>> 1. Remove rest/thrift from 2.3
>>>>> 1a. Proceed with 2.3.0 rc's
>>>>> 2. Add rest/thrift to hbase-connectors
>>>>> ...
>>>>> n. Release hbase-connectors
>>>>>
>>>>> I'm not a fan of removing anything which was previously there until
>>>>> there is are new releases and documentation to tell me how to do it.
>> I'm
>>>>> still trying to help dig out another project who did the 'remove and
>>>>> then migrate" and left a pile of busted.
>>>>>
>>>>> If that's not what you were suggesting, let me shirk back into the
>>>>> shadows;)
>>>>>
>>>>
>>>> Ha ha. Not what I was suggesting but that could for sure happen.
>>>>
>>>> S
>>>>
>>>> P.S. I'm having trouble w/ REST jersey1 vs jersey2 vs Hadoop3 transitive
>>>> includes++. Thrift has sporadic test failures that seem inherent to
>> thrift
>>>> rather of our manufacture. The discussion here was provoked by a
>> daydream
>>>> that bringing forward this inevitable migration of REST+thrift would
>>>> 'solve' my immediate pain. Wasn't giving too much mind to the amount of
>>>> work needed on the other side.
>>>
>>> I’m not clear on how moving the module out will resolve the class path
>>> issues. Whether it’s built from the main repo or from the side repo,
>> yarn’s
>>> transitive hull is still present...
>>>
>>
>> Yeah, understandable :)
>>
>> I think working with "something" for REST/Thrift in connectors (punt on
>> H3 to start?) is reasonable. You shouldn't be stuck with the baggage of
>> Jersey dependencies if that's not the problem you're trying to solve.
>>
> 

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Nick Dimiduk <nd...@apache.org>]

I suppose an alternative is to provide a shaded version of the YARN jars
needed by hbase-rest in hbase-thirdparty. We'd need these for both hadoop2
and hadoop3, to pull them in via profile, and to exclude the originals
wherever they appear as transitive deps (though they shouldn't, right?)

On Mon, Apr 27, 2020 at 11:24 AM Josh Elser <el...@apache.org> wrote:

>
>
> On 4/27/20 1:52 PM, Nick Dimiduk wrote:
> > On Mon, Apr 27, 2020 at 10:11 Stack<st...@duboce.net>  wrote:
> >
> >> On Mon, Apr 27, 2020 at 9:44 AM Josh Elser<el...@apache.org>  wrote:
> >>
> >>> +1 to the idea, -0 to the implied execution
> >>>
> >>> I agree hbase-connectors is a better place for REST and thrift, long
> >> term.
> >>> My concern is that I read this thread as suggesting:
> >>>
> >>> 1. Remove rest/thrift from 2.3
> >>> 1a. Proceed with 2.3.0 rc's
> >>> 2. Add rest/thrift to hbase-connectors
> >>> ...
> >>> n. Release hbase-connectors
> >>>
> >>> I'm not a fan of removing anything which was previously there until
> >>> there is are new releases and documentation to tell me how to do it.
> I'm
> >>> still trying to help dig out another project who did the 'remove and
> >>> then migrate" and left a pile of busted.
> >>>
> >>> If that's not what you were suggesting, let me shirk back into the
> >>> shadows;)
> >>>
> >>
> >> Ha ha. Not what I was suggesting but that could for sure happen.
> >>
> >> S
> >>
> >> P.S. I'm having trouble w/ REST jersey1 vs jersey2 vs Hadoop3 transitive
> >> includes++. Thrift has sporadic test failures that seem inherent to
> thrift
> >> rather of our manufacture. The discussion here was provoked by a
> daydream
> >> that bringing forward this inevitable migration of REST+thrift would
> >> 'solve' my immediate pain. Wasn't giving too much mind to the amount of
> >> work needed on the other side.
> >
> > I’m not clear on how moving the module out will resolve the class path
> > issues. Whether it’s built from the main repo or from the side repo,
> yarn’s
> > transitive hull is still present...
> >
>
> Yeah, understandable :)
>
> I think working with "something" for REST/Thrift in connectors (punt on
> H3 to start?) is reasonable. You shouldn't be stuck with the baggage of
> Jersey dependencies if that's not the problem you're trying to solve.
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Josh Elser <el...@apache.org>]

On 4/27/20 1:52 PM, Nick Dimiduk wrote:
> On Mon, Apr 27, 2020 at 10:11 Stack<st...@duboce.net>  wrote:
> 
>> On Mon, Apr 27, 2020 at 9:44 AM Josh Elser<el...@apache.org>  wrote:
>>
>>> +1 to the idea, -0 to the implied execution
>>>
>>> I agree hbase-connectors is a better place for REST and thrift, long
>> term.
>>> My concern is that I read this thread as suggesting:
>>>
>>> 1. Remove rest/thrift from 2.3
>>> 1a. Proceed with 2.3.0 rc's
>>> 2. Add rest/thrift to hbase-connectors
>>> ...
>>> n. Release hbase-connectors
>>>
>>> I'm not a fan of removing anything which was previously there until
>>> there is are new releases and documentation to tell me how to do it. I'm
>>> still trying to help dig out another project who did the 'remove and
>>> then migrate" and left a pile of busted.
>>>
>>> If that's not what you were suggesting, let me shirk back into the
>>> shadows;)
>>>
>>
>> Ha ha. Not what I was suggesting but that could for sure happen.
>>
>> S
>>
>> P.S. I'm having trouble w/ REST jersey1 vs jersey2 vs Hadoop3 transitive
>> includes++. Thrift has sporadic test failures that seem inherent to thrift
>> rather of our manufacture. The discussion here was provoked by a daydream
>> that bringing forward this inevitable migration of REST+thrift would
>> 'solve' my immediate pain. Wasn't giving too much mind to the amount of
>> work needed on the other side.
> 
> I’m not clear on how moving the module out will resolve the class path
> issues. Whether it’s built from the main repo or from the side repo, yarn’s
> transitive hull is still present...
> 

Yeah, understandable :)

I think working with "something" for REST/Thrift in connectors (punt on 
H3 to start?) is reasonable. You shouldn't be stuck with the baggage of 
Jersey dependencies if that's not the problem you're trying to solve.

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Nick Dimiduk <nd...@apache.org>]

On Mon, Apr 27, 2020 at 10:11 Stack <st...@duboce.net> wrote:

> On Mon, Apr 27, 2020 at 9:44 AM Josh Elser <el...@apache.org> wrote:
>
> > +1 to the idea, -0 to the implied execution
> >
> > I agree hbase-connectors is a better place for REST and thrift, long
> term.
> >
> > My concern is that I read this thread as suggesting:
> >
> > 1. Remove rest/thrift from 2.3
> > 1a. Proceed with 2.3.0 rc's
> > 2. Add rest/thrift to hbase-connectors
> > ...
> > n. Release hbase-connectors
> >
> > I'm not a fan of removing anything which was previously there until
> > there is are new releases and documentation to tell me how to do it. I'm
> > still trying to help dig out another project who did the 'remove and
> > then migrate" and left a pile of busted.
> >
> > If that's not what you were suggesting, let me shirk back into the
> > shadows ;)
> >
>
>
> Ha ha. Not what I was suggesting but that could for sure happen.
>
> S
>
> P.S. I'm having trouble w/ REST jersey1 vs jersey2 vs Hadoop3 transitive
> includes++. Thrift has sporadic test failures that seem inherent to thrift
> rather of our manufacture. The discussion here was provoked by a daydream
> that bringing forward this inevitable migration of REST+thrift would
> 'solve' my immediate pain. Wasn't giving too much mind to the amount of
> work needed on the other side.


I’m not clear on how moving the module out will resolve the class path
issues. Whether it’s built from the main repo or from the side repo, yarn’s
transitive hull is still present...

> On 4/25/20 7:44 PM, Stack wrote:
> > > On Fri, Apr 24, 2020 at 10:06 PM Sean Busbey<bu...@apache.org>
> wrote:
> > >
> > >> By "works with it" do you mean has documented steps to work with it or
> > do
> > >> you mean that the convenience binary that ships for 2.3.0 will have
> the
> > >> same deployment model as prior 2.y releases where I can run those
> > services
> > >> directly from the download?
> > >>
> > >>
> > > Former. Not the latter. They would no-longer be part of the hbase-2.3.x
> > > distribution.
> > > S
> > >
> > >
> > >
> > >
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Stack <st...@duboce.net>]

On Mon, Apr 27, 2020 at 9:44 AM Josh Elser <el...@apache.org> wrote:

> +1 to the idea, -0 to the implied execution
>
> I agree hbase-connectors is a better place for REST and thrift, long term.
>
> My concern is that I read this thread as suggesting:
>
> 1. Remove rest/thrift from 2.3
> 1a. Proceed with 2.3.0 rc's
> 2. Add rest/thrift to hbase-connectors
> ...
> n. Release hbase-connectors
>
> I'm not a fan of removing anything which was previously there until
> there is are new releases and documentation to tell me how to do it. I'm
> still trying to help dig out another project who did the 'remove and
> then migrate" and left a pile of busted.
>
> If that's not what you were suggesting, let me shirk back into the
> shadows ;)
>


Ha ha. Not what I was suggesting but that could for sure happen.

S

P.S. I'm having trouble w/ REST jersey1 vs jersey2 vs Hadoop3 transitive
includes++. Thrift has sporadic test failures that seem inherent to thrift
rather of our manufacture. The discussion here was provoked by a daydream
that bringing forward this inevitable migration of REST+thrift would
'solve' my immediate pain. Wasn't giving too much mind to the amount of
work needed on the other side.



> On 4/25/20 7:44 PM, Stack wrote:
> > On Fri, Apr 24, 2020 at 10:06 PM Sean Busbey<bu...@apache.org>  wrote:
> >
> >> By "works with it" do you mean has documented steps to work with it or
> do
> >> you mean that the convenience binary that ships for 2.3.0 will have the
> >> same deployment model as prior 2.y releases where I can run those
> services
> >> directly from the download?
> >>
> >>
> > Former. Not the latter. They would no-longer be part of the hbase-2.3.x
> > distribution.
> > S
> >
> >
> >
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Josh Elser <el...@apache.org>]

+1 to the idea, -0 to the implied execution

I agree hbase-connectors is a better place for REST and thrift, long term.

My concern is that I read this thread as suggesting:

1. Remove rest/thrift from 2.3
1a. Proceed with 2.3.0 rc's
2. Add rest/thrift to hbase-connectors
...
n. Release hbase-connectors

I'm not a fan of removing anything which was previously there until 
there is are new releases and documentation to tell me how to do it. I'm 
still trying to help dig out another project who did the 'remove and 
then migrate" and left a pile of busted.

If that's not what you were suggesting, let me shirk back into the 
shadows ;)

On 4/25/20 7:44 PM, Stack wrote:
> On Fri, Apr 24, 2020 at 10:06 PM Sean Busbey<bu...@apache.org>  wrote:
> 
>> By "works with it" do you mean has documented steps to work with it or do
>> you mean that the convenience binary that ships for 2.3.0 will have the
>> same deployment model as prior 2.y releases where I can run those services
>> directly from the download?
>>
>>
> Former. Not the latter. They would no-longer be part of the hbase-2.3.x
> distribution.
> S
> 
> 
> 
> 

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Josh Elser <el...@apache.org>]

+1 to the idea, -0 to the implied execution

I agree hbase-connectors is a better place for REST and thrift, long term.

My concern is that I read this thread as suggesting:

1. Remove rest/thrift from 2.3
1a. Proceed with 2.3.0 rc's
2. Add rest/thrift to hbase-connectors
...
n. Release hbase-connectors

I'm not a fan of removing anything which was previously there until 
there is are new releases and documentation to tell me how to do it. I'm 
still trying to help dig out another project who did the 'remove and 
then migrate" and left a pile of busted.

If that's not what you were suggesting, let me shirk back into the 
shadows ;)

On 4/25/20 7:44 PM, Stack wrote:
> On Fri, Apr 24, 2020 at 10:06 PM Sean Busbey<bu...@apache.org>  wrote:
> 
>> By "works with it" do you mean has documented steps to work with it or do
>> you mean that the convenience binary that ships for 2.3.0 will have the
>> same deployment model as prior 2.y releases where I can run those services
>> directly from the download?
>>
>>
> Former. Not the latter. They would no-longer be part of the hbase-2.3.x
> distribution.
> S
> 
> 
> 
> 

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Stack <st...@duboce.net>]

On Fri, Apr 24, 2020 at 10:06 PM Sean Busbey <bu...@apache.org> wrote:

> By "works with it" do you mean has documented steps to work with it or do
> you mean that the convenience binary that ships for 2.3.0 will have the
> same deployment model as prior 2.y releases where I can run those services
> directly from the download?
>
>
Former. Not the latter. They would no-longer be part of the hbase-2.3.x
distribution.
S




> On Fri, Apr 24, 2020, 16:34 Stack <st...@duboce.net> wrote:
>
> > Taking a sounding....
> >
> > We've talked of moving the hbase-rest and hbase-thrift modules out of
> core
> > over to hbase-connectors project [2, 3]. The connectors project [1] was
> > meant for the likes of REST and thrift. I'm thinking of trying to do the
> > move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> > release from hbase-connectors as part of this effort and would make sure
> it
> > works w/ 2.3.0.
> >
> > Thank you,
> > S
> >
> >
> > 1. https://github.com/apache/hbase-connectors
> > 2. https://issues.apache.org/jira/browse/HBASE-20999
> > 3. https://issues.apache.org/jira/browse/HBASE-20998
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Nick Dimiduk <nd...@apache.org>]

On Fri, Apr 24, 2020 at 22:06 Sean Busbey <bu...@apache.org> wrote:

> By "works with it" do you mean has documented steps to work with it or do
> you mean that the convenience binary that ships for 2.3.0 will have the
> same deployment model as prior 2.y releases where I can run those services
> directly from the download?


I would not suggest packaging hbase-connectors into the hbase(-core)
tarball. Instead, I would recommend some accommodation akin to (or perhaps
simpler than) what we do with hbck2. Perhaps we can add a env variable that
is the path to the unpacked connectors tarball. This can be sniffed in
`bin/hbase` to retain support for the existing `bin/hbase <service>
<action>` commands.

I do think we’d need to have a release of connectors before we release
core, if this is indeed the desired path.

On Fri, Apr 24, 2020, 16:34 Stack <st...@duboce.net> wrote:
>
> > Taking a sounding....
> >
> > We've talked of moving the hbase-rest and hbase-thrift modules out of
> core
> > over to hbase-connectors project [2, 3]. The connectors project [1] was
> > meant for the likes of REST and thrift. I'm thinking of trying to do the
> > move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> > release from hbase-connectors as part of this effort and would make sure
> it
> > works w/ 2.3.0.
> >
> > Thank you,
> > S
> >
> >
> > 1. https://github.com/apache/hbase-connectors
> > 2. https://issues.apache.org/jira/browse/HBASE-20999
> > 3. https://issues.apache.org/jira/browse/HBASE-20998
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Stack <st...@duboce.net>]

On Fri, Apr 24, 2020 at 10:06 PM Sean Busbey <bu...@apache.org> wrote:

> By "works with it" do you mean has documented steps to work with it or do
> you mean that the convenience binary that ships for 2.3.0 will have the
> same deployment model as prior 2.y releases where I can run those services
> directly from the download?
>
>
Former. Not the latter. They would no-longer be part of the hbase-2.3.x
distribution.
S




> On Fri, Apr 24, 2020, 16:34 Stack <st...@duboce.net> wrote:
>
> > Taking a sounding....
> >
> > We've talked of moving the hbase-rest and hbase-thrift modules out of
> core
> > over to hbase-connectors project [2, 3]. The connectors project [1] was
> > meant for the likes of REST and thrift. I'm thinking of trying to do the
> > move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> > release from hbase-connectors as part of this effort and would make sure
> it
> > works w/ 2.3.0.
> >
> > Thank you,
> > S
> >
> >
> > 1. https://github.com/apache/hbase-connectors
> > 2. https://issues.apache.org/jira/browse/HBASE-20999
> > 3. https://issues.apache.org/jira/browse/HBASE-20998
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Nick Dimiduk <nd...@apache.org>]

On Fri, Apr 24, 2020 at 22:06 Sean Busbey <bu...@apache.org> wrote:

> By "works with it" do you mean has documented steps to work with it or do
> you mean that the convenience binary that ships for 2.3.0 will have the
> same deployment model as prior 2.y releases where I can run those services
> directly from the download?


I would not suggest packaging hbase-connectors into the hbase(-core)
tarball. Instead, I would recommend some accommodation akin to (or perhaps
simpler than) what we do with hbck2. Perhaps we can add a env variable that
is the path to the unpacked connectors tarball. This can be sniffed in
`bin/hbase` to retain support for the existing `bin/hbase <service>
<action>` commands.

I do think we’d need to have a release of connectors before we release
core, if this is indeed the desired path.

On Fri, Apr 24, 2020, 16:34 Stack <st...@duboce.net> wrote:
>
> > Taking a sounding....
> >
> > We've talked of moving the hbase-rest and hbase-thrift modules out of
> core
> > over to hbase-connectors project [2, 3]. The connectors project [1] was
> > meant for the likes of REST and thrift. I'm thinking of trying to do the
> > move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> > release from hbase-connectors as part of this effort and would make sure
> it
> > works w/ 2.3.0.
> >
> > Thank you,
> > S
> >
> >
> > 1. https://github.com/apache/hbase-connectors
> > 2. https://issues.apache.org/jira/browse/HBASE-20999
> > 3. https://issues.apache.org/jira/browse/HBASE-20998
> >
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Sean Busbey <bu...@apache.org>]

By "works with it" do you mean has documented steps to work with it or do
you mean that the convenience binary that ships for 2.3.0 will have the
same deployment model as prior 2.y releases where I can run those services
directly from the download?

On Fri, Apr 24, 2020, 16:34 Stack <st...@duboce.net> wrote:

> Taking a sounding....
>
> We've talked of moving the hbase-rest and hbase-thrift modules out of core
> over to hbase-connectors project [2, 3]. The connectors project [1] was
> meant for the likes of REST and thrift. I'm thinking of trying to do the
> move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> release from hbase-connectors as part of this effort and would make sure it
> works w/ 2.3.0.
>
> Thank you,
> S
>
>
> 1. https://github.com/apache/hbase-connectors
> 2. https://issues.apache.org/jira/browse/HBASE-20999
> 3. https://issues.apache.org/jira/browse/HBASE-20998
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Jan Hentschel <ja...@ultratendency.com>]

+1

From: "张铎(Duo Zhang)" <pa...@gmail.com>
Reply-To: "dev@hbase.apache.org" <de...@hbase.apache.org>
Date: Saturday, April 25, 2020 at 3:20 AM
To: HBase Dev List <de...@hbase.apache.org>
Cc: Hbase-User <us...@hbase.apache.org>
Subject: Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

+1.

Andrew Purtell <ap...@apache.org>> 于2020年4月25日周六 上午5:50写道：

+1
Let's do it.

On Fri, Apr 24, 2020 at 2:34 PM Stack <st...@duboce.net>> wrote:

> Taking a sounding....
>
> We've talked of moving the hbase-rest and hbase-thrift modules out of
core
> over to hbase-connectors project [2, 3]. The connectors project [1] was
> meant for the likes of REST and thrift. I'm thinking of trying to do the
> move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> release from hbase-connectors as part of this effort and would make sure
it
> works w/ 2.3.0.
>
> Thank you,
> S
>
>
> 1. https://github.com/apache/hbase-connectors
> 2. https://issues.apache.org/jira/browse/HBASE-20999
> 3. https://issues.apache.org/jira/browse/HBASE-20998
>


--
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
    - A23, Crosstalk

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Jan Hentschel <ja...@ultratendency.com>]

+1

From: "张铎(Duo Zhang)" <pa...@gmail.com>
Reply-To: "dev@hbase.apache.org" <de...@hbase.apache.org>
Date: Saturday, April 25, 2020 at 3:20 AM
To: HBase Dev List <de...@hbase.apache.org>
Cc: Hbase-User <us...@hbase.apache.org>
Subject: Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

+1.

Andrew Purtell <ap...@apache.org>> 于2020年4月25日周六 上午5:50写道：

+1
Let's do it.

On Fri, Apr 24, 2020 at 2:34 PM Stack <st...@duboce.net>> wrote:

> Taking a sounding....
>
> We've talked of moving the hbase-rest and hbase-thrift modules out of
core
> over to hbase-connectors project [2, 3]. The connectors project [1] was
> meant for the likes of REST and thrift. I'm thinking of trying to do the
> move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> release from hbase-connectors as part of this effort and would make sure
it
> works w/ 2.3.0.
>
> Thank you,
> S
>
>
> 1. https://github.com/apache/hbase-connectors
> 2. https://issues.apache.org/jira/browse/HBASE-20999
> 3. https://issues.apache.org/jira/browse/HBASE-20998
>


--
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
    - A23, Crosstalk

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

["张铎 (Duo Zhang)" <pa...@gmail.com>]

+1.

Andrew Purtell <ap...@apache.org> 于2020年4月25日周六 上午5:50写道：

> +1
> Let's do it.
>
> On Fri, Apr 24, 2020 at 2:34 PM Stack <st...@duboce.net> wrote:
>
> > Taking a sounding....
> >
> > We've talked of moving the hbase-rest and hbase-thrift modules out of
> core
> > over to hbase-connectors project [2, 3]. The connectors project [1] was
> > meant for the likes of REST and thrift. I'm thinking of trying to do the
> > move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> > release from hbase-connectors as part of this effort and would make sure
> it
> > works w/ 2.3.0.
> >
> > Thank you,
> > S
> >
> >
> > 1. https://github.com/apache/hbase-connectors
> > 2. https://issues.apache.org/jira/browse/HBASE-20999
> > 3. https://issues.apache.org/jira/browse/HBASE-20998
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>    - A23, Crosstalk
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

["张铎 (Duo Zhang)" <pa...@gmail.com>]

+1.

Andrew Purtell <ap...@apache.org> 于2020年4月25日周六 上午5:50写道：

> +1
> Let's do it.
>
> On Fri, Apr 24, 2020 at 2:34 PM Stack <st...@duboce.net> wrote:
>
> > Taking a sounding....
> >
> > We've talked of moving the hbase-rest and hbase-thrift modules out of
> core
> > over to hbase-connectors project [2, 3]. The connectors project [1] was
> > meant for the likes of REST and thrift. I'm thinking of trying to do the
> > move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> > release from hbase-connectors as part of this effort and would make sure
> it
> > works w/ 2.3.0.
> >
> > Thank you,
> > S
> >
> >
> > 1. https://github.com/apache/hbase-connectors
> > 2. https://issues.apache.org/jira/browse/HBASE-20999
> > 3. https://issues.apache.org/jira/browse/HBASE-20998
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>    - A23, Crosstalk
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Andrew Purtell <ap...@apache.org>]

+1
Let's do it.

On Fri, Apr 24, 2020 at 2:34 PM Stack <st...@duboce.net> wrote:

> Taking a sounding....
>
> We've talked of moving the hbase-rest and hbase-thrift modules out of core
> over to hbase-connectors project [2, 3]. The connectors project [1] was
> meant for the likes of REST and thrift. I'm thinking of trying to do the
> move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> release from hbase-connectors as part of this effort and would make sure it
> works w/ 2.3.0.
>
> Thank you,
> S
>
>
> 1. https://github.com/apache/hbase-connectors
> 2. https://issues.apache.org/jira/browse/HBASE-20999
> 3. https://issues.apache.org/jira/browse/HBASE-20998
>


-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Andrew Purtell <ap...@apache.org>]

+1
Let's do it.

On Fri, Apr 24, 2020 at 2:34 PM Stack <st...@duboce.net> wrote:

> Taking a sounding....
>
> We've talked of moving the hbase-rest and hbase-thrift modules out of core
> over to hbase-connectors project [2, 3]. The connectors project [1] was
> meant for the likes of REST and thrift. I'm thinking of trying to do the
> move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> release from hbase-connectors as part of this effort and would make sure it
> works w/ 2.3.0.
>
> Thank you,
> S
>
>
> 1. https://github.com/apache/hbase-connectors
> 2. https://issues.apache.org/jira/browse/HBASE-20999
> 3. https://issues.apache.org/jira/browse/HBASE-20998
>


-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Stack <st...@duboce.net>]

Update.

I seem to be over the bulk of my difficulty getting thrift/rest to behave
in the hadoop3/jdk11 context though there are still some stragglers.
Because of this I am thinking of doing the move after 2.3.x, for 2.4.x,
instead. I'll run the scenario Josh suggests of an hbase-connectors release
first that packages thrift/rest.

At move time, let me mess w/ the suggestions below of shedding dependencies
on the likes of YARN and of updating REST to (shaded?) jersey2, etc.

Thanks,
S


On Fri, Apr 24, 2020 at 2:33 PM Stack <st...@duboce.net> wrote:

> Taking a sounding....
>
> We've talked of moving the hbase-rest and hbase-thrift modules out of core
> over to hbase-connectors project [2, 3]. The connectors project [1] was
> meant for the likes of REST and thrift. I'm thinking of trying to do the
> move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> release from hbase-connectors as part of this effort and would make sure it
> works w/ 2.3.0.
>
> Thank you,
> S
>
>
> 1. https://github.com/apache/hbase-connectors
> 2. https://issues.apache.org/jira/browse/HBASE-20999
> 3. https://issues.apache.org/jira/browse/HBASE-20998
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Stack <st...@duboce.net>]

Update.

I seem to be over the bulk of my difficulty getting thrift/rest to behave
in the hadoop3/jdk11 context though there are still some stragglers.
Because of this I am thinking of doing the move after 2.3.x, for 2.4.x,
instead. I'll run the scenario Josh suggests of an hbase-connectors release
first that packages thrift/rest.

At move time, let me mess w/ the suggestions below of shedding dependencies
on the likes of YARN and of updating REST to (shaded?) jersey2, etc.

Thanks,
S


On Fri, Apr 24, 2020 at 2:33 PM Stack <st...@duboce.net> wrote:

> Taking a sounding....
>
> We've talked of moving the hbase-rest and hbase-thrift modules out of core
> over to hbase-connectors project [2, 3]. The connectors project [1] was
> meant for the likes of REST and thrift. I'm thinking of trying to do the
> move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> release from hbase-connectors as part of this effort and would make sure it
> works w/ 2.3.0.
>
> Thank you,
> S
>
>
> 1. https://github.com/apache/hbase-connectors
> 2. https://issues.apache.org/jira/browse/HBASE-20999
> 3. https://issues.apache.org/jira/browse/HBASE-20998
>

Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?

[Sean Busbey <bu...@apache.org>]

By "works with it" do you mean has documented steps to work with it or do
you mean that the convenience binary that ships for 2.3.0 will have the
same deployment model as prior 2.y releases where I can run those services
directly from the download?

On Fri, Apr 24, 2020, 16:34 Stack <st...@duboce.net> wrote:

> Taking a sounding....
>
> We've talked of moving the hbase-rest and hbase-thrift modules out of core
> over to hbase-connectors project [2, 3]. The connectors project [1] was
> meant for the likes of REST and thrift. I'm thinking of trying to do the
> move in the next few days BEFORE 2.3.0RC0. Any objections? I'd make a
> release from hbase-connectors as part of this effort and would make sure it
> works w/ 2.3.0.
>
> Thank you,
> S
>
>
> 1. https://github.com/apache/hbase-connectors
> 2. https://issues.apache.org/jira/browse/HBASE-20999
> 3. https://issues.apache.org/jira/browse/HBASE-20998
>