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