t; > redeployed the job with new configs. I was assuming that it would get
> > incremented with every deployment/update.
> >
> > Thanks,
> > David
> >
> > On Wed, Aug 24, 2016 at 5:39 PM David Yu <david...@optimizely.com>
> wrote:
> >
>
oesn't seem to change. It stays at 1 even after I
> redeployed the job with new configs. I was assuming that it would get
> incremented with every deployment/update.
>
> Thanks,
> David
>
> On Wed, Aug 24, 2016 at 5:39 PM David Yu <david...@optimizely.com> wrote:
>
> &
th new configs. I was assuming that it would get
incremented with every deployment/update.
Thanks,
David
On Wed, Aug 24, 2016 at 5:39 PM David Yu <david...@optimizely.com> wrote:
> Hi,
>
> I'm trying to understand role of the coordinator stream during a job
> redeployment.
>
>
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 periodica
