[
https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935327#comment-15935327
]
Mayuresh Gharat edited comment on KAFKA-4808 at 3/21/17 9:00 PM:
-----------------------------------------------------------------
[~ijuma] Please find the KIP here :
https://cwiki.apache.org/confluence/display/KAFKA/KIP-135+%3A+Send+of+null+key+to+a+compacted+topic+should+throw+non-retriable+error+back+to+user.
was (Author: mgharat):
[~ijuma] Please find the KIP here :
https://cwiki.apache.org/confluence/display/KAFKA/Send+of+null+key+to+a+compacted+topic+should+throw+non-retriable+error+back+to+user.
> 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
> Fix For: 0.11.0.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
(v6.3.15#6346)
