[
https://issues.apache.org/jira/browse/HADOOP-12547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992364#comment-14992364
]
Allen Wittenauer commented on HADOOP-12547:
-------------------------------------------
bq. The Java client APIs provide significant advantages that neither streaming
nor pipes provide.
This is a false statement. Partitioning, for example, can't be done natively in
streaming code but can in pipes. In streaming, you can only provide a Java
class.
bq. In fact, they don't even mention streaming at all. In fact, they don't
even mention streaming at all. Again I ask, why would you personally ever use
or recommend pipes when streaming is available?
Correct. Because if the code is being written MR in C++, why would one use the
less functional streaming API? If one believes that MR jobs consist of nothing
but reading and writing KVs I could see that, but there's a lot more going on
under the hood in more advanced jobs. That functionality is just flat-out not
available in streaming.
BTW, thanks to this discourse, I realize that yes, not deprecating until trunk
is completely the correct thing to do. It clearly fills a gap not fulfilled by
any other APIs. So, I'm more convinced that ever that a -1 is appropriate here.
> Deprecate 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)
