[
https://issues.apache.org/jira/browse/KAFKA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Reisman updated KAFKA-367:
------------------------------
Attachment: KAFKA-367-5.patch
This includes the Encoder/Decoder improvement as in the 367-4 patch, and the
Consumer and Producer console options to set character encoding manually and
place it into the relevant Properties objects for consumption inside Kafka.
Passes SBT tests etc. should be good to go?
> 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, KAFKA-367-4.patch, KAFKA-367-5.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
