[jira] [Commented] (SAMZA-448) Pass config from JobRunner to JobCoordinator via ConfigStream

["Chris Riccomini (JIRA)" <ji...@apache.org>]

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

Chris Riccomini commented on SAMZA-448:
---------------------------------------

Now that we're actually going to write code for this, we need to be concrete on the name. Three options:

# ConfigStream
# MetadataStream
# ControlStream

Thoughts [~closeuris], [~sriramsub], [~martinkl], [~cpsoman], [~theduderog]?

> 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)