jerrypeng commented on pull request #9895: URL: https://github.com/apache/pulsar/pull/9895#issuecomment-803019382
The problem seems to be with `getSchema()` in Record and the subsequent `getSchema()` on the actual pulsar message. For consumer declared like Consumer<byte[]>, getSchema() calls on messages the consumer returns will always be SCHEMA.BYTES, regardless of what the actual schema the message was produced with. The schema of message is overridden when byte[] is specified as the schema for the consumer. This seems like a bug to me. Perhaps @sijie can also chime in on why the behavior is such. If messages returned by a Consumer<byte[]> had the right schema, i.e. the schema of the topic / schema the message was produced with, then your problem is solved right @eolivelli ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
