[
https://issues.apache.org/jira/browse/BEAM-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276654#comment-15276654
]
Jesse Anderson commented on BEAM-165:
-------------------------------------
There is more MR than Spark out there. I think not having the possibility of MR
now adds an ops requirement. That makes the potential customer have to put a
Spark/Flink cluster in production before they can start using Beam. It will
make the argument for moving to Beam more difficult.
> Add a 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.4#6332)
