[
https://issues.apache.org/jira/browse/KAFKA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111024#comment-16111024
]
Aish Raj Dahal commented on KAFKA-2526:
---------------------------------------
[~ewencp] Apologies for the naivety, but I was thinking along the lines
throwing an error as well. Additionally, like mentioned in the original issue
description as well as one of your earlier comments, creating a KIP for
cleaning up the configs in the console producer and the console consumer is
what I was planning along. As a user of the command line tools, having a
simpler interface to passing the configuration parameters and getting the right
error messages for unexpected behavior would surely make my day :)
Let me know how this sounds to you. Since I'm fairly new to the community,
perhaps out of nativity I am underestimating the effort involved, particularly
for the later of of the task i.e., in getting the KIP approved and working on.
Suggestions/tips around this are welcome!
> 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)
