[
https://issues.apache.org/jira/browse/HDFS-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163878#comment-14163878
]
Colin Patrick McCabe commented on HDFS-7200:
--------------------------------------------
bq. I prefer libhdfs++ than libndfs. The first name retains the information
that it is evolution of libhdfs. Lets say we come up another iteration of
libhdfs, how would that be named. A number after libhdfs is better than ++ that
way. I agree this a bikeshed argument. But it should not unnecessary add more
confusion.
I don't think this library is an evolution of {{libhdfs}}.
libhdfs is basically a generic JNI access library. It should have been called
something like libhadoop_jni_fs, because it's not HDFS-specific at all.
On the other hand, this library is hdfs-specific, and always will be. So maybe
it has a valid claim to be called libhdfs. But that name is already taken, so
I proposed libndfs++ to emphasize that it is fully native, unlike the existing
libhdfs.
Do plus signs in file names work properly on all platforms? I keep finding
stuff like this:
http://oidatsmyleg.wordpress.com/2010/02/15/dont-include-a-plus-sign-in-filenames-for-files-uploaded-to-sharepoint/
> Rename libhdfs3 to libndfs++
> ----------------------------
>
> Key: HDFS-7200
> URL: https://issues.apache.org/jira/browse/HDFS-7200
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Affects Versions: HADOOP-10388
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-7200.001.patch
>
>
> Since we generally agree that libhdfs3 is a sub-optimal name, let's call the
> new library "libndfs++."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
