Hello, Pulsar community:

Now, we use Avro Schema with Logical type, and the client
automatically adds logical type conversion. You can see PR
https://github.com/apache/pulsar/pull/6704.

But  AUTO_CONSUME Schema with Avro doesn't add the logical type
conversion.  It makes the Time type decode to Long.
We have two ways to solve the problem:
1. Added configuration control whether to add. This doesn't bring
compatibility issues.
2. Do not add configuration to control, add directly like Avro Schema.
It will bring compatibility issues

I prefer option 2 because it is a bug in itself. We don't need to
consider compatibility. Otherwise, schema loses its meaning.

What do you think, leave your opinion :)

Thanks
Bo,

Reply via email to