Cast error when Typed Persistence Actor received Old Commands


We’re trying to do a rolling update which involve an old typed persistence actor and a new typed persistence actor. We have implemented them totally independent from each other and has independent command, events, state and reply classes.

The problem is when we do a rolling update from a version with the old typed persistence actor to a version with the new old typed persistence actor, we’ve encountered a casting error.

My question is, if there’s away to intercept the old command message on the new typed persistence actor before casting it to the new command message?