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

Hudson commented on HADOOP-8395:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #2254 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2254/])
    HADOOP-8395. Text shell command unnecessarily demands that a SequenceFile's 
key class be WritableComparable (harsh) (Revision 1337449)

     Result = ABORTED
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1337449
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/shell/Display.java

                
> Text shell command unnecessarily demands that a SequenceFile's key class be 
> WritableComparable
> ----------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8395
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8395
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 2.0.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Trivial
>              Labels: shell
>             Fix For: 3.0.0
>
>         Attachments: HADOOP-8395.patch
>
>
> Text from Display set of Shell commands (hadoop fs -text), has a strict 
> subclass check for a sequence-file-header loaded key class to be a subclass 
> of WritableComparable.
> The sequence file writer itself has no such checks (one can create sequence 
> files with just plain writable keys, comparable is needed for sequence file's 
> sorter alone, which not all of them use always), and hence its not reasonable 
> for Text command to carry it either.
> We should relax the check and simply just check for "Writable", not 
> "WritableComparable".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to