Re: Printing to stdin from KStreams?

Nice idea. :-) Happy to hear it works for you, and thanks for sharing your workaround with the mailing list. On Fri, Oct 7, 2016 at 5:33 PM, Ali Akhtar wrote: > Thank you. > > I've resolved this by adding a run config in Intellij for running > streams-reset, and using the

Re: Printing to stdin from KStreams?

Thank you. I've resolved this by adding a run config in Intellij for running streams-reset, and using the same application id in all applications in development (transparently reading the application id from environment variables, so in my kubernetes config I can specify different app ids for

Re: Printing to stdin from KStreams?

> Is it possible to have kafka-streams-reset be automatically called during > development? Something like streams.cleanUp() but which also does reset? Unfortunately this isn't possible (yet), Ali. I am also not aware of any plan to add such a feature in the short-term. On Fri, Oct 7, 2016 at

Re: Printing to stdin from KStreams?

Is it possible to have kafka-streams-reset be automatically called during development? Something like streams.cleanUp() but which also does reset? On Fri, Oct 7, 2016 at 2:45 PM, Michael Noll wrote: > Ali, > > adding to what Matthias said: > > Kafka 0.10 changed the

Re: Printing to stdin from KStreams?

Ali, adding to what Matthias said: Kafka 0.10 changed the message format to add so-called "embedded timestamps" into each Kafka message. The Java producer included in Kafka 0.10 includes such embedded timestamps into any generated message as expected. However, other clients (like the go kafka

Re: Printing to stdin from KStreams?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 If you restart your application, it will resume where is left off (same as any other Kafka consumer that does use group management and commits offsets). If you want to reprocess data from scratch, you need to reset your application using

Re: Printing to stdin from KStreams?

Thanks. I'm encountering a strange issue. If I create messages thru console-producer.sh on a new topic, things work fine. But on the topic that I need to consume, the messages are being produced via the go kafka plugin. On this topic, at first, nothing happens when the stream starts (i.e it

Re: Printing to stdin from KStreams?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Sure. Just use #print() or #writeAsText() - -Matthias On 10/6/16 6:25 PM, Ali Akhtar wrote: > What the subject says. For dev, it would be a lot easier if > debugging info can be printed to stdin instead of another topic, > where it will persist.

Printing to stdin from KStreams?

What the subject says. For dev, it would be a lot easier if debugging info can be printed to stdin instead of another topic, where it will persist. Any ideas if this is possible?