You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2019/02/17 19:15:01 UTC
[jira] [Commented] (KAFKA-4808) send of null key to a compacted
topic should throw error back to user
[ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770582#comment-16770582 ]
Matthias J. Sax commented on KAFKA-4808:
----------------------------------------
Moving all major/minor/trivial tickets that are not merged yet out of 2.2 release.
> send of null key to a compacted topic should throw error back to user
> ---------------------------------------------------------------------
>
> Key: KAFKA-4808
> URL: https://issues.apache.org/jira/browse/KAFKA-4808
> Project: Kafka
> Issue Type: Bug
> Components: producer
> Affects Versions: 0.10.2.0
> Reporter: Ismael Juma
> Assignee: Mayuresh Gharat
> Priority: Major
> Fix For: 2.2.0
>
>
> If a message with a null key is produced to a compacted topic, the broker returns `CorruptRecordException`, which is a retriable exception. As such, the producer keeps retrying until retries are exhausted or request.timeout.ms expires and eventually throws a TimeoutException. This is confusing and not user-friendly.
> We should throw a meaningful error back to the user. From an implementation perspective, we would have to use a non retriable error code to avoid this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)