cc'ed from dev
-------- Forwarded Message -------- Subject: Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API Date: Sat, 4 Feb 2017 11:30:46 -0800 From: Matthias J. Sax <matth...@confluent.io> Organization: Confluent Inc To: d...@kafka.apache.org I think the right pattern should be to use TopologyBuilder as a class member, like new KStreamBuilder will do, instead of a class hierarchy, in case you want to offer your own higher level abstraction to describe a topology. Why is it important that you can derive a new class from it? I am not too strict about about. It's just a suggestion to make it final to enforce a different usage pattern, that IMHO is better than the current one. -Matthias On 2/3/17 5:15 PM, radai wrote: > why is it so important to make those classes final ? > > On Fri, Feb 3, 2017 at 3:33 PM, Matthias J. Sax <matth...@confluent.io> > wrote: > >> Hi All, >> >> I did prepare a KIP to do some cleanup some of Kafka's Streaming API. >> >> Please have a look here: >> https://cwiki.apache.org/confluence/display/KAFKA/KIP- >> 120%3A+Cleanup+Kafka+Streams+builder+API >> >> Looking forward to your feedback! >> >> >> -Matthias >> >> >
signature.asc
Description: OpenPGP digital signature
