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] [Commented] (KAFKA-367) StringEncoder/StringDecoder use platform default character set
Date Thu, 06 Sep 2012 18:01:11 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449868#comment-13449868
] 

Eli Reisman commented on KAFKA-367:
-----------------------------------

Sorry, that makes sense. Wasn't sure if that was "to be added later when someone needs it"
or if that should be wired up now. Will do. Kind of felt like the constructor should have
been in the trait rather than the classes too but the compiler didn't agree. Might try another
swipe at getting that to happen too. 
                
> 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