[
https://issues.apache.org/jira/browse/HADOOP-12547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989763#comment-14989763
]
Allen Wittenauer commented on HADOOP-12547:
-------------------------------------------
bq. If we are going to keep this, I would like to see some unit tests,
documentation, and actual maintenance.
This pretty much sums up my feelings towards libwebhdfs as well, yet we're
keeping it around because someone, somewhere might have fixed the compilation
issues (hint: it's still broken in this recent 2.6 release) and is actually
using it.
I see no reason to remove pipes if we're not also removing libwebhdfs. The
reasons to remove are pretty much identical, but at least pipes a) has compiled
for most of its lifetime and b) we have evidence that people are actually
looking at it.
So from where I stand, they either both go or both stay.
> Remove hadoop-pipes
> -------------------
>
> Key: HADOOP-12547
> URL: https://issues.apache.org/jira/browse/HADOOP-12547
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
>
> Development appears to have stopped on hadoop-pipes upstream for the last few
> years, aside from very basic maintenance. Hadoop streaming seems to be a
> better alternative, since it supports more programming languages and is
> better implemented.
> There were no responses to a message on the mailing list asking for users of
> Hadoop pipes... and in my experience, I have never seen anyone use this. We
> should remove it to reduce our maintenance burden and build times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
