In the past we've had discussions even about kicking out the connector modules (hbase-rest, hbase-thrift) so this begs the question why take on the contribution as opposed to let it live as a separate GitHub project? That said, in my opinion the answer depends on to what degree we want to support a technology connector which can drive adoption. The REST gateway gets used quite a bit. The Thrift gateway is the only multi-language high performance connector option where JVM integration isn't available. I think announcing a Kafka integration would generate interest in HBase itself as a persistence option where it might not have been considered otherwise, so taking on the maintenance commitment implied by integrating this module could pay dividends. For that reason I would be +1
On Mon, Jul 23, 2018 at 3:35 PM Stack <[email protected]> wrote: > We have a very nice contrib sitting up in HBASE-15320 which via a proxy -- > so minimal dependencies -- adds source and sink for Kafka Connect. It is > nicely contained inside two new hbase-kafka-* modules. > > We good w/ taking on this new feature? > > It looks good to me. Check it out up on HBASE-15320. I was going to commit > to tip of branch-2 so it'd show up in hbase-2.2.x unless you all want some > backporting action going on. > > S > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
