I see. Yeah, I don't see how we could provide such a generic serde for Jackson. The java classes themselves are not portable, so the fully-qualified name would be a terrible protocol for sharing data across applications. The current "type identifier" is a little more portable, but it would still be a super awkward protocol for data sharing.
Personally, I think something like this is good for quick-and-dirty prototyping, but ultimately, I'd recommend anyone to use something like Avro for production: 1. json is far more wasteful than binary serialization on the wire and in the broker 2. we are basically storing the "schema" in every single record via "_t", which is also wasteful. It's much better to store the schema externally and just map it to the topic somehow. [ Full content available at: https://github.com/apache/kafka/pull/5590 ] This message was relayed via gitbox.apache.org for [email protected]
