In general, all changes to transforms and coders are expected to allow
users to update to the latest Beam version. Different runners serialize at
different points, so we typically just assume the encoding and transform
layout must remain the same.
I am pretty confident that in the case of ResourceIds they definitely are
serialized in places that would break users if the encoding changed.
Kenn
On Thu, Jun 3, 2021 at 8:26 AM Matt Rudary wrote:
> My general question is what responsibility we have to maintain forward and
> backward compatibility for serialization of objects in the SDK. My specific
> question is about org.apache.beam.sdk.io.aws.s3.S3ResourceId – how can I
> tell whether ResourceIds are serialized anywhere that would require stable
> serialization across Beam SDK updates?
>
>
>
> Thanks
>
