[
https://issues.apache.org/jira/browse/HADOOP-9164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572002#comment-13572002
]
Colin Patrick McCabe commented on HADOOP-9164:
----------------------------------------------
Hi Owen,
I tend to agree with you that {{libhadoop.so}} should have the same version
number as the jars do. It's just more consistent. Why don't we open up a
separate JIRA just for that? It sounds like a small change to you or I, but in
reality it involves pulling in the bigtop people (who rely on the current
naming scheme) and a bunch of other folks.
On the other hand, printing out the full path to the library in
{{NativeLibraryChecker}} is just an HDFS-internal issue which we can easily do.
There's no reason why the two changes should be coupled, and I feel like the
request to do so is blocking progress.
It's pretty common to have multiple copies of {{libhadoop.so}} on the same
node. For me personally, knowing the full path to the library actually being
used is much more useful than the library version number. Even if we redefine
the {{libhadoop.so}} version number to be the same as the release number, that
just means I will have a probably always be set to {{3.0.0-SNAPSHOT}} or the
CDH version number. I could have known that I was using {{3.0.0-SNAPSHOT}}
just by looking at the name of the jars in my path.
> 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, HADOOP-9164.v4.2.patch, HADOOP-9164.v4.patch,
> HADOOP-9164.v4.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
