Re: Kafka Streams debugging with "no fluent" API choice

What do you think ? > > > > > > Thanks > > > > > > Paolo Patierno > > Senior Software Engineer (IoT) @ Red Hat > > Microsoft MVP on Windows Embedded & IoT > > Microsoft Azure Advisor > > > > Twitter : @ppatierno<http://twitter

Re: Kafka Streams debugging with "no fluent" API choice

_ From: Damian Guy <damian@gmail.com> Sent: Tuesday, August 1, 2017 2:11 PM To: dev@kafka.apache.org Subject: Re: Kafka Streams debugging with "no fluent" API choice Hi Paolo, The change would require a KIP as it is a public API change. I don't see any harm in mak

Re: Kafka Streams debugging with "no fluent" API choice

: DevExperience<http://paolopatierno.wordpress.com/> > > > ________ > From: Damian Guy <damian@gmail.com> > Sent: Tuesday, August 1, 2017 12:11 PM > To: dev@kafka.apache.org > Subject: Re: Kafka Streams debugging with "no fluent&quo

Re: Kafka Streams debugging with "no fluent" API choice

ust 1, 2017 12:11 PM To: dev@kafka.apache.org Subject: Re: Kafka Streams debugging with "no fluent" API choice I don't know specifically why this is removed, however if you want to get the same functionality you can use peek, i.e: stream.map(...).peek(...).filter(..) You can log the key v

Re: Kafka Streams debugging with "no fluent" API choice

I don't know specifically why this is removed, however if you want to get the same functionality you can use peek, i.e: stream.map(...).peek(...).filter(..) You can log the key values out in the peek call. On Tue, 1 Aug 2017 at 11:48 Paolo Patierno wrote: > Hi guys, > > >

Kafka Streams debugging with "no fluent" API choice

Hi guys, I was thinking about Kafka Streams debug features and why the print() method overloads didn't return a KStream, in order to have a fluent DSL construction even during debugging, but just void. Then I came across this PR : https://github.com/apache/kafka/pull/1187 May I ask why