Suresh Balla

Hi @Nevon, we haven't updated anything else, all current schemas works good in older version of schema registry. This issue is happening only when we migrate to version 2. And...

I see RecordNameStrategy is being used a default strategy with this library.

I have further investigated this and found issue with MAGIC_BYTE inside encode method. I have reviewed the Java deserialisation code from confluent schema registry and it uses hex 0x0. Where...

Probably within node environment, both are the same, but on Java client we get exception if we do not explicitly mention hex as encoding in nodejs. Also I am wondering...

Okay, I will keep investigating this issue. We just do not want to restrict messages produced by this library can only ready by consumer using this same library. In the...

@tulios sure. Here is the sample one that we are using for testing purpose `{ "name": "IntegrationEventData", "type": "record", "namespace": "com.company.model", "fields": [ { "name": "dateTimeOccurred", "type": "string", "default": "null"...

I am also having same issue, looks like there is no active support for this project. I see @erjain helping most of the issues, can you help us here @erjain...