You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Prateek Maheshwari (JIRA)" <ji...@apache.org> on 2017/04/17 03:09:41 UTC

[jira] [Updated] (SAMZA-1130) ApplicationRunner for running StreamApplication

     [ https://issues.apache.org/jira/browse/SAMZA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prateek Maheshwari updated SAMZA-1130:
--------------------------------------
    Fix Version/s: 0.13.0

> ApplicationRunner for running StreamApplication
> -----------------------------------------------
>
>                 Key: SAMZA-1130
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1130
>             Project: Samza
>          Issue Type: New Feature
>    Affects Versions: 0.13.0
>            Reporter: Xinyu Liu
>            Assignee: Xinyu Liu
>             Fix For: 0.13.0
>
>
> ApplicationRunner is the layer between high fluent API and physical execution. It is responsible for planning execution, materializing the streams and configs, and running the physical execution. For Samza, we will provide three kinds of ApplicationRunners:
>  - RemoteApplicationRunner: this is for running Samza applications on remote clusters such as Yarn
>  - LocalApplicationRunner: this is for running Samza applications on locally (coordination may be needed among local processors)
>  - TestApplicationRunner: this is for running Samza applications in the testing environment which can support input sources for testing such as collections or files.



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