I'm looking into the code of AvroCoder, and I was wondering what happens when users upgrade Beam for streaming pipelines?
As I understand it, we should be able to deserialize coder from previous Beam version. Looking into guava vendoring, it's going to break serialization when we are going to switch guava version because the current version is a part of the namespace: import org.apache.beam.vendor.guava.v26_0_jre.com.google.common.base.Supplier; import org.apache.beam.vendor.guava.v26_0_jre.com.google.common.base.Suppliers; We don't have tests for it, but probably we already broke compatibility when we vendored guava. Can anybody clarify what would be the approach for coders?
