bug: Pulsar source failed when parsing avro message.

[liurenjie1024]

No description provided.

[xiangjinwu]

FYI #12871 unless using confluent schema registry, which is unlikely the case for pulsar, because pulsar has its own schema registry.

[liurenjie1024]

FYI #12871 unless using confluent schema registry, which is unlikely the case for pulsar, because pulsar has its own schema registry.

Yes, according to our debug with pulsar team, this is caused by wrong api usage.

[liurenjie1024]

Duplicated #12871

[xiangjinwu]

FYI #12871 unless using confluent schema registry, which is unlikely the case for pulsar, because pulsar has its own schema registry.

Yes, according to our debug with pulsar team, this is caused by wrong api usage.

Which usage do we intend to support then? (1) No header; (2) Single-object encoding header; (3) pulsar schema registry?

[liurenjie1024]

FYI #12871 unless using confluent schema registry, which is unlikely the case for pulsar, because pulsar has its own schema registry.

Yes, according to our debug with pulsar team, this is caused by wrong api usage.

Which usage do we intend to support then? (1) No header; (2) Single-object encoding header; (3) pulsar schema registry?

If no schema registry, we should use single-object encoding.
I've not tested what's the behavior of pulsar java api when there is schema registry, we should test it first.