You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2013/05/03 22:24:21 UTC
[jira] [Commented] (HADOOP-9544) backport UTF8 encoding fixes to
branch-1
[ https://issues.apache.org/jira/browse/HADOOP-9544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648767#comment-13648767 ]
Chris Nauroth commented on HADOOP-9544:
---------------------------------------
Thanks, Nicholas. I'll report back when I have the test results. Here is the test-patch output. Regarding findbugs, it appears that the filterBugs command in test-patch.sh is not actually filtering out anything. I've seen mention of other people having this problem on the mailing lists. It's unrelated to this patch.
{code}
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 5 new or modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] -1 findbugs. The patch appears to introduce 427 new Findbugs (version 1.3.9) warnings.
{code}
> backport UTF8 encoding fixes to branch-1
> ----------------------------------------
>
> Key: HADOOP-9544
> URL: https://issues.apache.org/jira/browse/HADOOP-9544
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Affects Versions: 1.3.0
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-4795-branch-1.1.patch, HDFS-4795-branch-1.2.patch
>
>
> The trunk code has received numerous bug fixes related to UTF8 encoding. I recently observed a branch-1-based cluster fail to load its fsimage due to these bugs. I've confirmed that the bug fixes existing on trunk will resolve this, so I'd like to backport to branch-1.
--
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