On Fri, Apr 24, 2020 at 22:06 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?
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 <[email protected]> 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 > > >
