hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9801) Configuration#writeXml uses platform defaulting encoding, which may mishandle multi-byte characters.
Date Thu, 01 Aug 2013 19:31:49 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-9801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HADOOP-9801:
----------------------------------

    Attachment: HADOOP-9801-trunk.2.patch

bq. This seems to work for me: System.setProperty("file.encoding","Cp1252");

That's interesting.  Everything I read said that this wouldn't work.  Maybe I was reading
out-of-date docs.  Thanks for trying this out.

Here are new patches to set default encoding in the test, and then restore it to the prior
default at the end of the tests.  I used US-ASCII for the test instead of CP-1252, because
US-ASCII is required to be present in any spec-compliant JVM.

How does this look?

                
> Configuration#writeXml uses platform defaulting encoding, which may mishandle multi-byte
characters.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9801
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9801
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 3.0.0, 1-win, 1.3.0, 2.1.1-beta
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HADOOP-9801-branch-1.1.patch, HADOOP-9801-branch-1.2.patch, HADOOP-9801-trunk.1.patch,
HADOOP-9801-trunk.2.patch
>
>
> The overload of {{Configuration#writeXml}} that accepts an {{OutputStream}} does not
set encoding explicitly, so it chooses the platform default encoding.  Depending on the platform's
default encoding, this can cause incorrect output data when encoding multi-byte characters.

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