kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias J. Sax" <matth...@confluent.io>
Subject Re: kstream transform forward to different topics
Date Wed, 13 Feb 2019 18:53:15 GMT
The goal of KIP-307 is a different one. It's about providing names to
make debugging easier.

Thus, I don't think "307 is doing it the wrong way" -- the question is,
what problem is addressed, and KIP-307 addresses a different one as
discussed on this question.


-Matthias

On 2/13/19 1:53 AM, Jan Filipiak wrote:
> For now, just use the name it gets automatically, or crack the
> AbstractStream open with reflection ;)
> 
> 307 is doing it the wrong way again, just make name accessible instead
> of make the users put them :face_with_rolling_eyes:
> 
> On 08.02.2019 02:36, Guozhang Wang wrote:
>> Hi Nan,
>>
>> Glad it helps with your case. Just another note that in the next release
>> when KIP-307 is in place [1], you can actually combine the DSL with PAPI by
>> naming the last operator that creates your transformed KStream, and then
>> manually add the sink nodes like:
>>
>> stream2 = stream1.transform(Named.as("myName"));
>>
>> topology = builder.build();
>>
>> // continue adding to the built topology
>> topology.addSink(... "myName");
>>
>> -----


Mime
View raw message