[
https://issues.apache.org/jira/browse/HADOOP-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213088#comment-14213088
]
Chris Nauroth commented on HADOOP-11127:
----------------------------------------
bq. Apparently, we've made a prior decision to stop shipping a native build...
While validating the 2.6.0 release candidate, I noticed that we are in fact
still shipping a libhadoop.so in the binary distribution. Now I'm not sure
what our official policy is.
{code}
[cnauroth@ubuntu:pts/4] hadoop-2.6.0
> objdump -f lib/native/libhadoop.so
lib/native/libhadoop.so: file format elf64-x86-64
architecture: i386:x86-64, flags 0x00000150:
HAS_SYMS, DYNAMIC, D_PAGED
start address 0x0000000000005f20
{code}
> 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
> Attachments: HADOOP-11064.003.patch
>
>
> 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)
