kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4808) send of null key to a compacted topic should throw error back to user
Date Mon, 27 Feb 2017 18:46:45 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886297#comment-15886297

Ismael Juma commented on KAFKA-4808:

[~mgharat], I think a separate error code would be a better long-term solution because we
can then provide a specific error message. And yes, it would require a simple KIP. What do
you think?

> 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:
>            Reporter: Ismael Juma
>            Assignee: Mayuresh Gharat
>             Fix For:
> 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

View raw message