Hi All,
I found the below example on how branching can be achieved with kafka
streams. I want to implement the same with processor API and the way I get
it is to have the same input topic processed with multiple process
functions and output the data based on the filters. Is this the right
underst
I'll keep an eye on that and other topics in all my four environments to
see when it appears again For the moment it's fine
On 02-Oct-19 7:50 AM, M. Manna wrote:
I don’t think you can control replication using clients (pub/sub). And
neither should you be allowed to.
I guess we need more o
I don’t think you can control replication using clients (pub/sub). And
neither should you be allowed to.
I guess we need more of such examples to understand correct use if admin
API.
Thanks,
On Tue, 1 Oct 2019 at 19:45, Sebastian Schmitz <
sebastian.schm...@propellerhead.co.nz> wrote:
> I didn'
I didn't change anything with the topic... But as it only affects one
topic my idea would be that it's related to the publisher as it's
different for this specific topic.
Can a publisher tell Kafka what to do about replication? Like having
such an influence to have this kind of symptoms?
Als
I was going to ask you to do that :) As long as >1 replicas are in-sync
Kafka handles this nicely for recreating everything in the restarted broker.
I am curious, do you remember manipulating something before all these
started? e.g. Using some topic admin command (or something along the line) ?
