Hi Dong, I had thought about this before and wanted to do similar thing. But as was pointed out in the jira ticket, we wanted something more specific than general. The main issue is that we do not propagate server side error messages to clients, right now. I am working on a KIP proposal to propose it.
Thanks, Mayuresh On Mon, Mar 27, 2017 at 5:55 PM, Dong Lin <lindon...@gmail.com> wrote: > Hey Mayuresh, > > Thanks for the patch. I am wondering if it would be better to add a more > general error, e.g. InvalidMessageException. The benefit is that we can > reuse this for other message level error instead of adding one exception > class for each possible exception in the future. This is similar to the use > of InvalidRequestException. For example, ListOffsetResponse may return > InvalidRequestException if duplicate partitions are found in the > ListOffsetRequest. We don't return DuplicatedPartitionException in this > case. > > Thanks, > Dong > > > > On Wed, Mar 22, 2017 at 3:07 PM, Mayuresh Gharat < > gharatmayures...@gmail.com > > wrote: > > > Hi All, > > > > We have created KIP-135 to propose that Kafka should return a > non-retriable > > error when the producer produces a message with null key to a log > compacted > > topic. > > > > Please find the KIP wiki in the link : > > > > 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. > > > > > > We would love to hear your comments and suggestions. > > > > > > Thanks, > > > > Mayuresh > > > -- -Regards, Mayuresh R. Gharat (862) 250-7125
