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

Colin Patrick McCabe commented on HADOOP-11127:
-----------------------------------------------

bq. The trouble for hadoop-common.jar is that I have no idea how to make this 
play well with the Apache Hadoop release process. Apparently, we've made a 
prior decision to stop shipping a native build and leave this as a distro 
concern, such as in BigTop. We'd have to reverse that decision.

Yeah, we were supposed to stop shipping libhadoop.so in the tarball.  I looked 
at 
http://mirrors.ibiblio.org/apache/hadoop/common/hadoop-2.5.1/hadoop-2.5.1.tar.gz
 and it was still in there, which is kind of weird.  I wonder which platform 
the version in there is for?

If libhadoop.so isn't supposed to be in the tarball now, surely removing it 
isn't a regression?  We don't have a tarball per platform so it really doesn't 
make sense to put libhadoop in there.  I would like to see libhadoop.so make it 
back into the release (perhaps in the form of multiple flavors of 
{{hadoop-native.jar}} available for download?) but that seems like a separate 
issue which shouldn't block this issue.

> Improve versioning and compatibility support in native library for downstream 
> hadoop-common users.
> --------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11127
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11127
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: native
>            Reporter: Chris Nauroth
>
> There is no compatibility policy enforced on the JNI function signatures 
> implemented in the native library.  This library typically is deployed to all 
> nodes in a cluster, built from a specific source code version.  However, 
> downstream applications that want to run in that cluster might choose to 
> bundle a hadoop-common jar at a different version.  Since there is no 
> compatibility policy, this can cause link errors at runtime when the native 
> function signatures expected by hadoop-common.jar do not exist in 
> libhadoop.so/hadoop.dll.



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

Reply via email to