Re: Missing internal topic (partitions) after kafka-streams client upgrade (2.3.1 -> 2.4.0)

2019-12-26 Thread Matthias J. Sax
Thanks Nitay! We will investigate! -Matthias On 12/26/19 2:53 AM, Nitay Kufert wrote: > Also posted it at apache jira: > https://issues.apache.org/jira/browse/KAFKA-9335 > > On Thu, Dec 26, 2019 at 12:41 PM Nitay Kufert wrote: > >> I have made a "toy" example to reproduce this error, this is

Re: Kafka trunk vs master branch

2019-12-26 Thread Matthias J. Sax
Should we delete `master` ? (Was not even aware it exists...) -Matthias On 12/25/19 9:50 AM, M. Manna wrote: > +1 with what John mentioned. > > Master is more like a template that gets created for new repo. It’s not in > use for any Kafka activities (not that we know of). > > Regards, > > >

Re: Mirrormaker 2.0

2019-12-26 Thread Sebastian Schmitz
Hello Ryanne, Is there a way to prevent that from happening? We have two separate clusters with some topics being replicated to the second one for reporting. If we replicate everything again that reporting would probably have some problems. Yes, I wondered when the Networking-guys would come

Re: Missing internal topic (partitions) after kafka-streams client upgrade (2.3.1 -> 2.4.0)

2019-12-26 Thread Nitay Kufert
Also posted it at apache jira: https://issues.apache.org/jira/browse/KAFKA-9335 On Thu, Dec 26, 2019 at 12:41 PM Nitay Kufert wrote: > I have made a "toy" example to reproduce this error, this is more or less > what's going on in our application: >> >> package com.supersonic.bos.consumer >> >> i

Re: Missing internal topic (partitions) after kafka-streams client upgrade (2.3.1 -> 2.4.0)

2019-12-26 Thread Nitay Kufert
I have made a "toy" example to reproduce this error, this is more or less what's going on in our application: > > package com.supersonic.bos.consumer > > import java.time.Duration > import java.time.temporal.ChronoUnit > import java.util.Properties > import org.apache.kafka.common.serialization.Ser