You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2017/04/20 18:02:04 UTC
[jira] [Assigned] (BEAM-2026) High performance direct runner
[ https://issues.apache.org/jira/browse/BEAM-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Halperin reassigned BEAM-2026:
-------------------------------------
Assignee: Mitar (was: Thomas Groh)
> High performance direct runner
> ------------------------------
>
> Key: BEAM-2026
> URL: https://issues.apache.org/jira/browse/BEAM-2026
> Project: Beam
> Issue Type: New Feature
> Components: runner-direct
> Reporter: Mitar
> Assignee: Mitar
>
> In documentation (https://beam.apache.org/documentation/runners/direct/) it is written that direct runner does not try to run efficiently, but it serves mostly for development and debugging.
> I would suggest that there should be also an efficient direct runner. If Beam tries to be an unified programming model, for some smaller tasks I would love to implement them in Beam, just to keep the code in the same model, but it would be OK to run it as a normal smaller program (maybe inside one Docker container), without any distribution across multiple machines. In the future, if usage grows, I could then replace underlying runner with something distributed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)