[
https://issues.apache.org/jira/browse/HADOOP-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051808#comment-13051808
]
Todd Lipcon commented on HADOOP-7405:
-------------------------------------
I'm thinking it would just expect a particular version, and if you have an old
version on your system, it should refuse to load with an error logged.
Supporting past versions of the .so on new versions of Hadoop is a large matrix
to test -- we already do a bad job of testing native code.
If there are regressions with regard to OS support, we should catch those by
having people with strange OSes testing trunk and voting on releases. Building
a complicated framework into the code doesn't seem like the easiest solution to
me.
> libhadoop is all or nothing
> ---------------------------
>
> Key: HADOOP-7405
> URL: https://issues.apache.org/jira/browse/HADOOP-7405
> Project: Hadoop Common
> Issue Type: Bug
> Components: native
> Affects Versions: 0.20.203.0, 0.23.0
> Environment: Everything not Linux
> Reporter: Allen Wittenauer
> Priority: Blocker
> Labels: regression
>
> As a result of a ton of new code in libhadoop being added in 0.20.203/0.22, a
> lot of features that used to work no longer do reliably. The most common
> problem is native compression, but other issues such as Mac OS X's group
> support broke as well. The native code checks need to be refactored such
> that libhadoop.so should report what it supports rather than having the
> Java-side assume that if it loads, it is all supported. This would allow us
> to stub routines until they've been vetted, removing the chances of such
> regressions appearing in the future.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
