Sam Gendler

'The trick is to make sure there is a matching config file' is a pretty weak solution, since in many cases, there is no such config file to list. Additionally,...

You can work around this lack by registering your protos separately from using the schema registry. I use the maven plugin to run a registration step for all of my...

Since no one bothered to answer this - Confluent provide 3 ways to map from a topic to a schema registry topic. You MUST adhere to one of their 3...

When encoding a message for kafka and using schema registry, the first byte of the message should be a 0, and the next 4 bytes of the message should be...

In my experience, if you can see the message properly broken out in control center (except on confluent cloud, where control center doesn't parse messages correctly, yet), then it is...

it's also worth pointing out that the current implementation will not work at all for any protobuf which references another protobuf via an import statement, since it parses only the...

I have code which encodes it correctly. It isn't integrated with the schema registry client. I built a separate serializer so that I am using schema registry client only to...

On the decode side, it looks like this: ``` private decodeHeader(topic: string, buffer: Buffer): ProtoInfo { let bufferReader = Reader.create(buffer) const magicByte = bufferReader.uint32() const schemaId = HostOrder(bufferReader.fixed32()) const arrayLen...

I'll probably open-source the serializer and deserializer I built, but it's not likely to happen for a week or two.

I should elaborate - my code actually uses a pipeline to execute multiple custom commands. ``` cmd := pipe.Do(ctx, "CL.THROTTLE", req.key, req.maxBurst, req.limit, req.period*time.Second, 1) ``` which is eventually executed...