You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2014/09/26 17:51:34 UTC

[jira] [Updated] (HADOOP-11127) Improve versioning and compatibility support in native library for downstream hadoop-common users.

     [ https://issues.apache.org/jira/browse/HADOOP-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated HADOOP-11127:
-----------------------------------
    Attachment: HADOOP-11064.003.patch

To keep the discussion fully documented in this issue, I'm re-uploading the patch Colin had attached to HADOOP-11064 for versioning in the library's file name.  This can be considered a work-in-progress implementation of idea #2 in my first comment.  (I say work-in-progress, because we haven't addressed winutils.exe yet in this patch.)

> 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)