Re: [VOTE] KIP-349 Priorities for Source Topics

On Sat, Mar 23, 2019, at 18:41, nathank...@gmail.com wrote: > > > On 2019/01/28 02:26:31, n...@afshartous.com wrote: > > Hi Sönke, > > > > Thanks for taking the time to review. I’ve put KIP-349 into hibernation. > > > > Thanks also to everyone who participated in the discussion. > > > >

Jenkins build is back to normal : kafka-trunk-jdk8 #3492

See

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Ivan, Good point about the terminal operation being required. But is that really such a bad thing? If the user doesn't want a defaultBranch they can call some other terminal method (noDefaultBranch()?) just as easily. In fact I think it creates an opportunity for a nicer API - a user could

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Hello Paul, I afraid this won't work because we do not always need the defaultBranch. And without a terminal operation we don't know when to finalize and build the 'branch switch'. In my proposal, onTopOf returns its argument, so we can do something more with the original branch after

MirrorMaker 2.0 and Streams interplay (topic naming control)

Hi all, With MirrorMaker 2.0 ( https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0) accepted and coming along very nicely in development, it has got me wondering if a certain use case is supported, and if not, can changes be made to Streams or MM2 to support it. I'll

Re: [VOTE] KIP-349 Priorities for Source Topics

Hi Nathan, I have a couple of remarks/questions about your mail, if I may. First of all, the javadoc for the pause operation of KafkaConsumer states: "Suspend fetching from the requested partitions. Future calls to poll(Duration)