[
https://issues.apache.org/jira/browse/KAFKA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116726#comment-16116726
]
Ewen Cheslack-Postava commented on KAFKA-2526:
----------------------------------------------
[~ardahal] Yeah, I think the scope of the bug is just unclear. Adding better
errors would be a useful short-term stopgap solution (I think you just get a
cast exception or something like that if you try to set these to something
besides ByteArraySerializer, but I haven't double checked). The longer term
solution with a KIP is obviously a lot more involved, but you should feel free
to work on it; it would be a useful improvement. Since there would be two
separate steps, you'd probably want to either file a separate JIRA for the
better error messages and leave this one to the KIP or just file that fix as a
MINOR PR.
> Console Producer / Consumer's serde config is not working
> ---------------------------------------------------------
>
> Key: KAFKA-2526
> URL: https://issues.apache.org/jira/browse/KAFKA-2526
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Assignee: Mayuresh Gharat
> Labels: newbie
>
> Although in the console producer one can specify the key value serializer,
> they are actually not used since 1) it always serialize the input string as
> String.getBytes (hence always pre-assume the string serializer) and 2) it is
> actually only passed into the old producer. The same issues exist in console
> consumer.
> In addition the configs in the console producer is messy: we have 1) some
> config values exposed as cmd parameters, and 2) some config values in
> --producer-property and 3) some in --property.
> It will be great to clean the configs up in both console producer and
> consumer, and put them into a single --property parameter which could
> possibly take a file to reading in property values as well, and only leave
> --new-producer as the other command line parameter.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
