[
https://issues.apache.org/jira/browse/SAMZA-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14188502#comment-14188502
]
Sriram Subramanian commented on SAMZA-448:
------------------------------------------
The stream is an implementation detail and will never be exposed to the users.
The naming then becomes a choice w.r.t coding. We currently use the stream for
configs and offsets. We would use it in the future for sending other control
messages. I think all the three names are subjected to confusion (Config,
Control, Metadata). All these information are written into this stream so that
the controller can read it (In Yarn's case, it is the AM that uses the
controller library). I would call this the controller stream.
> Pass config from JobRunner to JobCoordinator via ConfigStream
> -------------------------------------------------------------
>
> Key: SAMZA-448
> URL: https://issues.apache.org/jira/browse/SAMZA-448
> Project: Samza
> Issue Type: Sub-task
> Components: container
> Affects Versions: 0.9.0
> Reporter: Chris Riccomini
> Assignee: Chris Riccomini
> Fix For: 0.9.0
>
>
> SAMZA-438 modified the AM/local job factories (job coordinator) to pass
> configuration to SamzaContainer via an HTTP server. This ticket is to modify
> the other half of the pipeline: the config passing from the JobRunner to the
> job coordinator to be done via a ConfigStream, rather than an environment
> variable.
> The goal of this ticket is to make the change as transparent as possible.
> {{control-job.sh}} won't be introduced in this ticket. Instead, we'll
> continue using the ConfigFactories that we have, but pass the resolved config
> to the coordinator using the ConfigStream rather than the environment
> variable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
