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

Steve Loughran commented on HADOOP-11064:
-----------------------------------------

I'm saying "if someone untars the hbase binaries and tries to use them in a 
hadoop 2.6 cluster, they get to see a stack trace". HBase includes all its 
JARs, which are 100% in sync, it's just that nobody bundles the native libs too.

I dont care about cross-JAR compatibility, but the changes in the .lib/.so code 
stop me running any hadoop 2.4 code if the 2.6 libs are on their LIBPATH. That 
includes standalone applications which would otherwise run happily without any 
native JARs. 


IMO those native bits of code are something we need to keep stable, even though 
they are never intended for direct public use. We should also have the java 
clients pick up version problems (2.6 code loading 2.4 lib)


> UnsatisifedLinkError with hadoop 2.4 JARs on hadoop-2.6 due 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
>            Priority: Blocker
>
> 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