eolivelli commented on pull request #9343: URL: https://github.com/apache/pulsar/pull/9343#issuecomment-768871076
> When we design Pulsar schema, we don't want to invent yet another type system. @sijie In Kafka Connect we see this great abstraction of [Schema](https://kafka.apache.org/11/javadoc/org/apache/kafka/connect/data/Schema.html) and this makes it very easy to implement Connectors (especially Sinks) in a way that is not dependant on the serialization mechanism. Therefore in Pulsar IO we do not allow the function implementation to access the underlying Avro libraries, I like this fact and I would like not to change it. So my thinking is that we need our way to describe a Schema with a Pulsar API. I would like also to follow up in order to add to the Pulsar Schema API all of the data types that are missing, like Arrays and Maps. In my opinion without these features Pulsar IO won't be able to compete with Kafka Connect, and also to "port" existing Kafka Connect workflows to the Pulsar Ecosystem ---------------------------------------------------------------- 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]
