[
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-2.patch
Another attempt. Also not working quite yet. I'm new to Scala and not quite
sure which syntax trick allows you to call a default constructor with and
without parens from client code, and to have an override with a string in the
constructor without upsetting Scala or the test code. This is happening in my
modifications to StringEncoder. I would ideally like to make the character
encoding setting a "val" as well. But all this will be solved soon I hope...
Feel free to take a look and advise a wayward Java refugee...
> 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
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
