I'm trying to understand the difference between Encoders/Decoders and
Serializers/Deserializers and when I should be using each. Specifically the
types I'm referring to are:
- kafka.serializer.Encoder
- kafka.serializer.Decoder
- org.apache.kafka.common.serialization.Serializer
- org.a
ee/master/avro-serializer/src/main/java/io/confluent/kafka/serializers
> which might help
>
> Not sure of the exact answer the to different between Encoder/Serializer
> though sorry.
>
> - Dan
>
>
> On 20 July 2015 at 17:39, Elliot West wrote:
>
> > I'm trying
Hello,
Apologies if this is a naïve question, but I'd like to understand if and
how KStreams and KSQL can deal with topics that reside in more than one
cluster. For example, is it possible for a single KS[treams|QL] application
to:
1. Source from a topic on cluster A
2. Produce/Consume to i
Hello,
I like to understand what strategies can be applied to migrate events,
producers, and consumers from one topic to another. Typically I'm thinking
of cases where:
- we wish to migrate a topic from one cluster to another
- high availability - minimise amount of time topic is unavailab
gt; *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> loss, damage or destruction of data or any other property which may arise
> from relying on this email's technical content is explicitly disclaimed.
> The author will in no case be liable for any monetary
Hello,
We're planning to adopt PEM over JKS for all of our Kafka Consumer and
Producer clients. Previously, with JKS, when a certificate was due to
expire, we could simply replace the JKS key store on disk with a renewed
cert and our producer/consumer instances would pick this up automatically
wit
I've captured this problem in JIRA:
https://issues.apache.org/jira/browse/KAFKA-13293
On Thu, 2 Sept 2021 at 09:58, Elliot West wrote:
> Hello,
>
> We're planning to adopt PEM over JKS for all of our Kafka Consumer and
> Producer clients. Previously, with JKS, when a
