Hi, I'm trying to understand role of the coordinator stream during a job redeployment.
>From the Samza documentation, I'm seeing the following about the coordinator stream: The Job Coordinator bootstraps configuration from the coordinator stream each time upon job start-up. It periodically catches up with any new data written to the coordinator stream and updates the Job Model. However, it is unclear to me how this will work with "--config-path" when we need to redeploy a job. Does the provided config first gets persisted to the coordinator stream, updating the previous model, or will it simply be ignored? Thanks, David
