beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Hogue (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (BEAM-165) Add Hadoop MapReduce runner
Date Thu, 23 Mar 2017 14:48:41 GMT

    [ https://issues.apache.org/jira/browse/BEAM-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938490#comment-15938490
] 

Michael Hogue edited comment on BEAM-165 at 3/23/17 2:47 PM:
-------------------------------------------------------------

[~eljefe6aa] is spot on. For heavy MR users looking to transition to a higher level API like
Beam, having a MR runner would make that transition much more smooth. 


was (Author: m-hogue):
[~eljefe6aa] is spot on. For heavy MR users looking to transition to a higher level API, having
a MR runner would make that transition much more smooth. 

> Add Hadoop MapReduce runner
> ---------------------------
>
>                 Key: BEAM-165
>                 URL: https://issues.apache.org/jira/browse/BEAM-165
>             Project: Beam
>          Issue Type: Wish
>          Components: runner-ideas
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> I think a MapReduce runner could be a good addition to Beam. It would allow users to
smoothly "migrate" from MapReduce to Spark or Flink.
> Of course, the MapReduce runner will run in batch mode (not stream).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message