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

Hadoop QA commented on HADOOP-6842:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12593076/HADOOP-6842.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/2816//console

This message is automatically generated.
                
> "hadoop fs -text" does not give a useful text representation of MapWritable 
> objects
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-6842
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6842
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: io
>    Affects Versions: 0.20.0
>            Reporter: Steven Wong
>         Attachments: HADOOP-6842.patch
>
>
> If a sequence file contains MapWritable objects, running "hadoop fs -text" on 
> the file prints the following for each MapWritable:
> org.apache.hadoop.io.MapWritable@4f8235ed
> To be more useful, it should print out the contents of the map instead. This 
> can be done by adding a toString method to MapWritable, i.e. something like:
> public String toString() {
>     return (new TreeMap<Writable, Writable>(instance)).toString();
> }

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

Reply via email to