[
https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975450#comment-15975450
]
ASF GitHub Bot commented on KAFKA-4808:
---------------------------------------
GitHub user MayureshGharat opened a pull request:
https://github.com/apache/kafka/pull/2875
KAFKA-4808 : Send of null key to a compacted topic should throw
non-retriable error back to user
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MayureshGharat/kafka KAFKA-4808
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2875.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2875
----
commit 731f1d1fedda5e09a8bd7094baf2e1572a3ba06e
Author: MayureshGharat <gharatmayures...@gmail.com>
Date: 2017-04-19T17:45:08Z
Added non retriable exception for producing record with null key to a
compacted topic
----
> 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)
