[
https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-4808:
---------------------------------
*Reminder to the contributor / reviewer of the PR*: please note that the code
deadline for 1.0.0 is less than 2 weeks away (Oct. 4th). Please re-evaluate
your JIRA and see if it still makes sense to be merged into 1.0.0 or it could
be pushed out to 1.1.0, or be closed directly if the JIRA itself is not valid
any more, or re-assign yourself as contributor / committer if you are no longer
working on the JIRA.
> 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: 1.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.4.14#64029)
