[
https://issues.apache.org/jira/browse/HADOOP-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500970#comment-14500970
]
Colin Patrick McCabe commented on HADOOP-11127:
-----------------------------------------------
I was thinking we:
1. Add the Hadoop release version to libhadoop.so. It's very, very simple and
solves a lot of problems here.
2. Remove libhadoop.so and libhdfs.so from the release tarball, since they are
CPU and OS-specific and the tarballs are not
3. Schedule some follow-on work to include the native libraries inside jars, as
Chris suggested. This will take longer but ultimately be the best solution.
> 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)
