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-9164) Add version number and/or library file name to native library for easy tracking
Date Wed, 02 Jan 2013 07:42:16 GMT

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

Allen Wittenauer commented on HADOOP-9164:
------------------------------------------

bq. Why not open a discussion on hadoop-dev about libhadoop.so version numbers?

I'm not sure what value there is in doing that. The version numbers are completely fictional,
confusing, and break with ancient UNIX traditions.  Just tying them back to the build version
a la OpenSSL would be a major step forward since that at least gives some clue about what
the compatibility expectations are.

bq.  I don't think this JIRA is the right place to sort that out.

As I said, I don't think there is anything controversial here.  Fixing it should be relatively
trivial (just read the generated java file and stuff it into the appropriate #define's and
make vars) and would allow the version of the patch that reports library versions to go forward.
 
                
> Add version number and/or library file name to native library for easy tracking
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-9164
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9164
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: native
>    Affects Versions: 2.0.2-alpha
>            Reporter: Binglin Chang
>            Assignee: Binglin Chang
>            Priority: Minor
>         Attachments: HADOOP-9164.v1.patch, HADOOP-9164.v2.patch, HADOOP-9164.v3.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message