Thank you Jeff for the quick reply. Does this mean, if a stateful job using the old coder wants to start using timer family id, then it needs to discard all its state first before it can switch to use V2 coder to have timer family id support?
Best, Ke > On Nov 6, 2020, at 11:27 AM, Jeff Klukas <jklu...@mozilla.com> wrote: > > Ke - You are correct that generally data encoded with a previous coder > version cannot be read with an updated coder. The formats have to match > exactly. > > As far as I'm aware, it's necessary to flush a job and start with fresh state > in order to upgrade coders. > > On Fri, Nov 6, 2020 at 2:13 PM Ke Wu <ke.wu...@gmail.com > <mailto:ke.wu...@gmail.com>> wrote: > Hello, > > I found that TimerDataCoderV2 is created to include timer family id and > output timestamps fields in TimerData. In addition, the new fields are > encoded between old fields, which I suppose V2 coder cannot decode and data > that is encoded by V1 coder and vice versus. My ask here is, how should we > properly upgrade without losing existing states persisted in a store? > > Best, > Ke
