You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2012/09/05 20:59:10 UTC
[jira] [Commented] (KAFKA-367) StringEncoder/StringDecoder use
platform default character set
[ https://issues.apache.org/jira/browse/KAFKA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449006#comment-13449006 ]
Jay Kreps commented on KAFKA-367:
---------------------------------
This looks good, but I don't see where we make use of the new constructor. I think we need to pass in the properties in the producer and consumer, right?
> StringEncoder/StringDecoder use platform default character set
> --------------------------------------------------------------
>
> Key: KAFKA-367
> URL: https://issues.apache.org/jira/browse/KAFKA-367
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Jay Kreps
> Assignee: Eli Reisman
> Labels: newbie
> Attachments: KAFKA-367-1.patch, KAFKA-367-2.patch, KAFKA-367-3.patch, KAFKA-367-3.patch
>
>
> StringEncoder and StringDecoder take the platform default character set. This is bad since the messages they produce are sent off that machine. We should
> -- add a new required argument to these that adds the character set and default to UTF-8 rather than the machine setting
> -- add a commandline parameter for the console-* tools to let you specify the correct encoding.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira