On Mon, Apr 27, 2020 at 9:44 AM Josh Elser <[email protected]> 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<[email protected]> 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 > > > > > > > > >
