[
https://issues.apache.org/jira/browse/SAMZA-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906893#comment-15906893
]
Navina Ramesh commented on SAMZA-1137:
--------------------------------------
[~nickpan47] I am not following why the ApplicationRunner should be available
in SamzaContainer. Are you by-passing the StreamProcessor abstraction
completely? Or does it only apply for Remote Runner implementations?
Either ways, it is really weird to pass ApplicationRunner down the stack. Can
you perhaps illustrate more on why this is required?
> Instantiate ApplicationRunner in SamzaContainer
> -----------------------------------------------
>
> Key: SAMZA-1137
> URL: https://issues.apache.org/jira/browse/SAMZA-1137
> Project: Samza
> Issue Type: Task
> Reporter: Yi Pan (Data Infrastructure)
>
> From the discussion on SAMZA-1122, we will need to create an
> ApplicationRunner in SamzaContainer as well, at least to provide StreamSpecs
> for fluent API.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
