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:03: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? This seems right and the decoder related tests seem to be passing, but
when I run the suite in SBT on my local machine I get several errors in tests regarding ZooKeeper.
I am unaware whether these are due to local test config or genuine trouble. They seem to culminate
at the Kafka end in Utils.getObject() at line 675.

                
> 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
>
>
> 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