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

Hudson commented on HIVE-2711:
------------------------------

Integrated in Hive-trunk-h0.21 #1428 (See 
[https://builds.apache.org/job/Hive-trunk-h0.21/1428/])
    HIVE-3018 Make the new header for RC Files introduced in HIVE-2711 optional
(Kevin Wilfong via namit) (Revision 1337937)

     Result = FAILURE
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1337937
Files : 
* /hive/trunk/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/io/RCFile.java
* /hive/trunk/ql/src/test/org/apache/hadoop/hive/ql/io/TestRCFile.java

                
> Make the header of RCFile unique
> --------------------------------
>
>                 Key: HIVE-2711
>                 URL: https://issues.apache.org/jira/browse/HIVE-2711
>             Project: Hive
>          Issue Type: Bug
>          Components: Serializers/Deserializers
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.10.0
>
>         Attachments: HIVE-2711.D2115.1.patch, HIVE-2711.D2115.2.patch, 
> HIVE-2711.D2115.3.patch, HIVE-2711.D2571.1.patch, rc-file-v0.rc
>
>
> The RCFile implementation was copied from Hadoop's SequenceFile and copied 
> the 'magic' string in the header. This means that you can't use the header to 
> distinguish between RCFiles and SequenceFiles.
> I'd propose that we create a new header for RCFiles (RCF?) to replace the 
> current SEQ. To maintain compatibility, we'll need to continue to accept the 
> current 'SEQ\06' and just make new files contain the new header.

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