hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7405) libhadoop is all or nothing
Date Mon, 20 Jun 2011 06:01:49 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051813#comment-13051813
] 

Allen Wittenauer commented on HADOOP-7405:
------------------------------------------

Ah, ok.  The soversion essentially moves lockstep with a given release.  If we were to go
to that method, we'd need to split libhadoop in half to fix the regression problem.

Granted, it is simple, but it doesn't necessarily prevent the problem that we've found ourselves.
 Unfortunately, I do not believe anyone on the PMC attempts to run non-Linux on a standard
basis.  Using release votes to prevent these situations from happening is pretty much a non-starter.


> 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

        

Mime
View raw message