Hi Carlos,
We would like for this update to be rejected on submission, as it is...
from: SerializableCoder.of(MessageWithAttributes.class[serialVersionUID=A])
to: SerializableCoder.of(MessageWithAttrbibutes.class[serialVersionUID=B])
... which are incompatible coders as far as the system can
Also I think this situation leads to a blocked status in which elements
with two different version UIDs are mixed and therefore unable to progress.
When I realised this was happening, I tried to rollback to the previous
version of the pipeline to drain it and then re-create the job with the new
Another thing I've realised is that the stacktrace suggests it is using
SerializerCoder instead of the MessageWithAttributesCoder custom one I have
implemented. See it here: https://pastebin.com/86gWddi9
Is it possible that, upon updates, custom coders are not chosen? To give a
little more
I've added a couple of methods to a case class and updated the job on
Dataflow and started getting
java.lang.IllegalStateException: Unable to decode tag list using
org.apache.beam.sdk.coders.SerializableCoder@4ad81832
Caused by java.io.InvalidClassException: my.package.MessageWithAttributes;
