[
https://issues.apache.org/jira/browse/KAFKA-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated KAFKA-8455:
-----------------------------------
Summary: Add VoidSerde to Serdes (was: Add NothingSerde to Serdes)
> Add VoidSerde to Serdes
> -----------------------
>
> Key: KAFKA-8455
> URL: https://issues.apache.org/jira/browse/KAFKA-8455
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: John Roesler
> Assignee: Nikolay Izhikov
> Priority: Minor
> Labels: beginner, needs-kip, newbie, newbie++
>
> Often, when reading an input topic, the key is expected to be null, but
> there's actually no way to represent this fact in Consumed, leading to
> confusing type signatures down the topology.
> For example, you might use the BytesSerde, but then you have a
> KStream<Bytes,...>. When maintaining a large application, this becomes a
> hazard, since you'd need to "be really careful" not to try and dereference
> the key at any point, since you actually know it's always null.
> Much better would be to actually represent the fact that the key is null,
> using the Void type. One such example of this is the NothingSerde I wrote
> here:
> https://github.com/confluentinc/kafka-streams-examples/blob/5.2.1-post/src/test/java/io/confluent/examples/streams/IntegrationTestUtils.java#L465
> After some conversations, I've come to believe this would actually be a
> useful addition to the main Serdes collection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
