+1 afaik, even basic extensions have problems with tranquillity at this point.
I started off with druid 6 months ago & was struggling to make datasketches work with tranquillity for a couple of days before realizing that a Kafka cluster in front is the right way. It'll only cause confusion for newcomers till clearly marked as deprecated. On Mon, 20 Jan 2020, 07:19 Fangjin Yang, <fang...@imply.io> wrote: > +1 > > On Sun, Jan 19, 2020 at 1:16 PM Jonathan Wei <jon...@apache.org> wrote: > > > Hi all, > > > > For the upcoming 0.17.0 release, I'm wondering if this would be a good > time > > to officially declare Tranquility as deprecated/sunsetted in the release > > notes. > > > > This was discussed a few times in the past, such as: > > > > > https://lists.apache.org/thread.html/476fdd5b6c681854df38bc78e5fae11d3fa371345e1924694ea6be4a%40%3Cdev.druid.apache.org%3E > > > > Tranquility hasn't had any updates and no on seems interested in > > maintaining it, it's been de-emphasized in the docs, and I think the > reply > > from Gian in that thread gives a good breakdown of the rationale for > > favoring Kafka ingestion instead: > > > > > We should include some rationale as to why that > > decision was made, too. To me the rationale boils down to: KIS style > > ingestion doesn't have a windowPeriod restriction, doesn't lose data when > > tasks fail, is lower footprint when reading from an external stream hub > > like Kafka/Kinesis, and has generally proven to be easier to set up and > > debug. > > > > Any thoughts? > > > > Best, > > Jon > > >
