[
https://issues.apache.org/jira/browse/HADOOP-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310870#comment-15310870
]
john lilley commented on HADOOP-11127:
--------------------------------------
My two cents; if there is some way to migrate shell-command/winutils calls into
a library I think this would reduce the number of opportunities for
configuration and environment error (see
https://issues.apache.org/jira/browse/HADOOP-13223, which is my laundry list of
gripes about how winutils causes various problems). I prefer approach #2 of
the three listed at the beginning. While it has some challenges, mostly
related to extracting a singleton of the .so/.dll in a multi-threaded
multi-process environment, it has the definite advantage of being able to find
and load exactly the library version we want.
> 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: Sub-task
> Components: native
> Reporter: Chris Nauroth
> Assignee: Alan Burlison
> Attachments: HADOOP-11064.003.patch, proposal.01.txt
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
