Re: SASL_PLAIN configuration problems

Hello Andrzej, The error: *NetworkClient - [Producer clientId=signings] Connection to node -1 (localhost/127.0.0.1:9093 ) failed authentication due to: Unexpected handshake request with client mechanism PLAIN, enabled mechanisms are []* It is complaining that your client is

Re: Kafka Streams - left join behavior

It's fixed in upcoming 3.1 release. Cf https://issues.apache.org/jira/browse/KAFKA-10847 A stream-(global)table join has different semantics, so I am not sure if it would help. One workaround would be to apply a stateful` faltTransformValues()` after the join to "buffer" all NULL-results an

Re: Event order in Kafka Streams after Left Join

I had heard when doing a join, the timestamp of the generated message is taken from the message triggering the join or the biggest timestamp of the two. In older versions it was the timestamp of the record that triggered the join. Since 2.3, it is the maximum of both (cf https://issues.apache

Mirrored repartition topics keep increasing in size

Hi, We are using MirrorMaker to backup topics. We noticed that repartition topics created by Kafka Streams applications seem to keep increasing in size in the target cluster compared to the source cluster. This makes sense according to the documentation of org.apache.kafka.streams.kstream.KStre