hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4032) Specify the charset explicitly rather than rely on the default
Date Tue, 08 Jan 2013 19:34:15 GMT

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

Eli Collins commented on HDFS-4032:
-----------------------------------

I don't think this is an issue because we don't run on jvm's that don't support UTF8 (hence
the assertion). Make sense?
                
> Specify the charset explicitly rather than rely on the default
> --------------------------------------------------------------
>
>                 Key: HDFS-4032
>                 URL: https://issues.apache.org/jira/browse/HDFS-4032
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0-alpha
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hdfs-4032.txt
>
>
> Findbugs 2 warns about relying on the default Java charset instead of specifying it explicitly.
Given that we're porting Hadoop to different platforms it's better to be explicit.

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