[
https://issues.apache.org/jira/browse/SAMZA-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899874#comment-15899874
]
Yi Pan (Data Infrastructure) commented on SAMZA-1122:
-----------------------------------------------------
Just to add some notes from our discussion offline:
# ApplicationRunner should support both low-level (task-level) programs and
programs using fluent APIs
# ApplicationRunner should support both local (i.e. within the same JVM
process) and remote (i.e. via a cluster manager like YARN) launch of Samza
applications
# ApplicationRunner should support shutdown and restart the Samza applications
in local mode, w/o shutting down the JVM process
# Currently, one ApplicationRunner will execute and control the lifecycle of
one Samza application instance
Users should always use ApplicationRunner to start the Samza application, after
the implementation of local and remote ApplicationRunner is completed.
> Rename ExecutionEnvironment to ApplicationRunner
> ------------------------------------------------
>
> Key: SAMZA-1122
> URL: https://issues.apache.org/jira/browse/SAMZA-1122
> Project: Samza
> Issue Type: Bug
> Reporter: Xinyu Liu
> Assignee: Xinyu Liu
>
> Some refactoring/cleanup:
> - rename ExecutionEnvironment to ApplicationRunner, including all the
> subclasses.
> - rename the package to be org.apache.samza.runtime
> - rename the StandalondApplicationRunner to be LocalApplicationRunner
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
