DanielLeens commented on issue #11211: URL: https://github.com/apache/seatunnel/issues/11211#issuecomment-4833545388
Thanks for opening this. I checked the current Pulsar connector path, and this looks like a reasonable feature request rather than a bug. The current gap is real: - Pulsar source only wires `JSON` / `CANAL_JSON` today - Pulsar sink is still documented and packaged around the existing `json` / `text` paths - Kafka already has working `AvroDeserializationSchema` / `AvroSerializationSchema` support, so this is more of a connector integration gap than a missing format foundation Since you already marked that you're willing to submit a PR and the issue has been assigned to you, the best next step is to keep the first implementation boundary tight: 1. add `format = avro` support for Pulsar source and sink 2. reuse the existing SeaTunnel Avro serialization / deserialization path instead of introducing a new format abstraction 3. add focused source / sink tests for the Avro path 4. update the en / zh Pulsar docs so the supported format matrix matches the code That would make this a good, reviewable first PR without mixing in broader Pulsar schema-registry or native-schema expansion at the same time. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
