You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Eric Chang (Jira)" <ji...@apache.org> on 2026/10/08 22:56:00 UTC

[jira] [Assigned] (KAFKA-21245) Support hex-encoded key/value in console consumer and producer

     [ https://issues.apache.org/jira/browse/KAFKA-21245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Chang reassigned KAFKA-21245:
----------------------------------

    Assignee: Eric Chang  (was: Chia-Ping Tsai)

> Support hex-encoded key/value in console consumer and producer
> --------------------------------------------------------------
>
>                 Key: KAFKA-21245
>                 URL: https://issues.apache.org/jira/browse/KAFKA-21245
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Chia-Ping Tsai
>            Assignee: Eric Chang
>            Priority: Minor
>              Labels: need-kip
>
> I was testing compacted topics and noticed that there is no official tool to write a tombstone for a specific record. The console producer can produce null values (KIP-810), but there is no way to type a binary key, so records with serialized keys (long, Avro, Protobuf, etc.) cannot be deleted from the command line.
> Of course, we can leverage AI to generate 1000 tools immediately, but “this tool” can be addressed by supporting hex 🙂
> Also, hex is the baseline for all types of records. It is line-safe, so the output can be piped through grep, awk, and other console tools, and it can be fed back into the console producer to reproduce the exact same bytes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)