You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/18 17:07:34 UTC

[jira] [Commented] (BEAM-165) Add Hadoop MapReduce runner

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

Beam JIRA Bot commented on BEAM-165:
------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Add Hadoop MapReduce runner
> ---------------------------
>
>                 Key: BEAM-165
>                 URL: https://issues.apache.org/jira/browse/BEAM-165
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-ideas, runner-mapreduce
>            Reporter: Jean-Baptiste Onofré
>            Priority: P2
>              Labels: stale-P2
>
> 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
(v8.3.4#803005)