[
https://issues.apache.org/jira/browse/HADOOP-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765154#action_12765154
]
Doug Cutting commented on HADOOP-6311:
--------------------------------------
Forking is certainly often not an optimal path. That said, forking is quite
different than using a snapshot build. In that case we committed the jar.
Here, Todd's proposing we commit the source, properly forking. We'd be taking
on the maintenance of this code, simply using the Android code as a starting
point. That might be warranted if Android is not a project that's in the
business of producing independent utility jar file releases, which it does not
appear to be.
If you agree with the above analysis, then the question has little to do with
the source of the code but rather with whether Hadoop's codebase should include
unix domain socket utilities. My general preference is to refactor later
rather than earlier: until we have another use of unix domain sockets within
Hadoop, or at least have another expected use, keep the code with its single
user in HDFS. Do you have another expected use?
> Add support for unix domain sockets to JNI libs
> -----------------------------------------------
>
> Key: HADOOP-6311
> URL: https://issues.apache.org/jira/browse/HADOOP-6311
> Project: Hadoop Common
> Issue Type: New Feature
> Components: native
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hadoop-6311.txt
>
>
> For HDFS-347 we need to use unix domain sockets. This JIRA is to include a
> library in common which adds a o.a.h.net.unix package based on the code from
> Android (apache 2 license)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
