beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Cwik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2026) High performance direct runner
Date Thu, 20 Apr 2017 16:10:04 GMT

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

Luke Cwik commented on BEAM-2026:
---------------------------------

Some runners have local execution modes like Flink and Spark, would this not be satisfactory?
If not, why not?

> 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: Thomas Groh
>
> 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)

Mime
View raw message