I am ok with officially deprecating or sunsetting Tranquility. Sunsetting may make more sense since a few of us are still committed to fixing critical bugs with it, but I don't know of anyone that is actively working on new features.
It was never part of the main Druid repo, so IMO all that really needs to be done is updating the Druid webpage (which references Tranquility in a few places), and the Tranquility repo itself, to say that Tranquility is deprecated/sunsetted and the recommended alternative is either the Kafka or Kinesis indexing service. 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. On Tue, Jan 15, 2019 at 4:03 AM Dylan Wylie <[email protected]> wrote: > Can attest on our clusters KIS has performed well enough to be considered > non-experimental. > > As part of its promotion, can we consider "officially" deprecating > Tranquility? Its status is a little uncertain post-apache and if there's > consensus on deprecating it it'd be good opportunity to collate what work > needs done to get there. > > > > On Tue, 15 Jan 2019 at 11:31, 邱明明 <[email protected]> wrote: > > > +1. > > > > Gian Merlino <[email protected]> 于2019年1月15日周二 上午6:18写道： > > > > > > I'd like to propose graduating a couple of features out of > 'experimental' > > > status in 0.14. Both are popular features (judging by mailing list & > > github > > > issue/PR activity). Both have been around for a while and have > attained a > > > good level of quality and stability of API & behavior. I believe > removing > > > the 'experimental' banner from these features would more accurately > > reflect > > > reality, and be a good signal to the user community. > > > > > > 1) Kafka indexing service. First introduced in Druid 0.9.1, it went > > through > > > a major protocol change in Druid 0.12.0 that added incremental > > publishing, > > > & 'mixing' of data from different partitions. Subjectively, quality > > appears > > > to be getting more solid, based on frequency of bug reports and also > > based > > > on our own experiences running this in production. Finally- I believe > it > > is > > > already much more robust than Tranquility, the only 'stable' > alternative. > > > > > > 2) Druid SQL. First introduced in Druid 0.10.0. It isn't feature > complete > > > yet (multi-value dimensions, datasketches, etc, remain unsupported) but > > the > > > API and behavior have been generally stable. No major issues around > > memory > > > / performance / etc regressions relative to native Druid queries are > > > outstanding. IMO, it is well on its way to becoming a first class way > to > > > query Druid, and it is a good time to remove the 'experimental' banner. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
