Pulsar schema doesn't do compatibility check for primitive types

[sijie]

Describe the bug

Currently Pulsar schema doesn't do compatibility check for primitive types. That says if a consumer connect to a topic with a different schema type. It still can connect and receive messages. Exception is only thrown when retrieving the values from the received messages.

To Reproduce
Steps to reproduce the behavior:

1. Send messages with Schema.STRING
2. Consume messages with Schema.INT32

Expected behavior

The consumer should be rejected when subscribing.

[codelipenghui]

@congbobo184 please take a look this issue.

[jiazhai]

@sijie @congbobo184 I am trying to do 2.4.1 release. How about move this into 2.5.0?

[sijie]

moved to 2.5.0

[congbobo184]

how we check compatibility for INT8 and INT16? we allow they decode the message for themself or allow INT16 read INT8? any suggestion can give to me ?

[sijie]

@congbobo184 to keep simple, we only check compatibilities when using same schema type. different schema types are always incompatible.

[congbobo184]

@congbobo184 to keep simple, we only check compatibilities when using same schema type. different schema types are always incompatible.
ok, i will do with what you mean :)