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

Hudson commented on HADOOP-11064:
---------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk #691 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/691/])
HADOOP-11064. UnsatisifedLinkError with hadoop 2.4 JARs on hadoop-2.6 due to 
NativeCRC32 method changes. Contributed by Chris Nauroth. (cnauroth: rev 
cbf0ae742ae3db964550df11c4044d3e16013959)
* 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestNativeCrc32.java
* 
hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/util/NativeCrc32.c
* 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/NativeCrc32.java
* hadoop-common-project/hadoop-common/CHANGES.txt


> UnsatisifedLinkError with hadoop 2.4 JARs on hadoop-2.6 due to NativeCRC32 
> method changes
> -----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11064
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11064
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: native
>    Affects Versions: 2.6.0
>         Environment: Hadoop 2.6 cluster, trying to run code containing hadoop 
> 2.4 JARs
>            Reporter: Steve Loughran
>            Assignee: Chris Nauroth
>            Priority: Blocker
>             Fix For: 2.6.0
>
>         Attachments: HADOOP-11064.001.patch, HADOOP-11064.002.patch, 
> HADOOP-11064.003.patch, HADOOP-11064.004.patch, HADOOP-11064.005.patch, 
> HADOOP-11064.006.patch
>
>
> The private native method names and signatures in {{NativeCrc32}} were 
> changed in HDFS-6561 ... as a result hadoop-common-2.4 JARs get unsatisifed 
> link errors when they try to perform checksums. 
> This essentially stops Hadoop 2.4 applications running on Hadoop 2.6 unless 
> rebuilt and repackaged with the hadoop- 2.6 JARs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to