e Advisor
>
> Twitter : @ppatierno<http://twitter.com/ppatierno>
> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
> Blog : DevExperience<http://paolopatierno.wordpress.com/>
>
>
> ____
> From: Damian Guy
> Sent: Tuesd
From: Damian Guy
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 making the
<http://paolopatierno.wordpress.com/>
>
>
> ____________________
> From: Damian Guy
> Sent: Tuesday, August 1, 2017 12:11 PM
> To: dev@kafka.apache.org
> Subject: Re: Kafka Streams debugging with "no fluent" API choice
>
> I don't know s
ev@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 values out in t
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,
>
>
> I was thinking about
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 the
