kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-367) StringEncoder/StringDecoder use platform default character set
Date Wed, 05 Sep 2012 04:05:07 GMT

     [ 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-3.patch

Is this more like it? I am still getting an error on several tests on SBT but they are ZooKeeper
tests and I'm not certain if they relate directly to this patch or my local setup is not right
for running the tests? They culminate on the Kafka side of the code in 2 ZK tests at Utils.getObject()
line 675. Does this ring any bells?

Thanks!


                
> 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

Mime
View raw message