[Bug]: Remove Spanner exclusion once bug is fixed

[damccorm]

What happened?

Right now, we pin to an older version of spanner to fix GoogleCloudPlatform/DataflowTemplates#3222

After the underlying problem is fixed, we should remove this exclusion

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[Abhishekmishra2808]

.take-issue

I would like to work on this. I am monitoring the upstream fix in GoogleCloudPlatform/DataflowTemplates#3222.

My proposed plan:

• Identify the specific version pin for google-cloud-spanner in the build configuration (likely in BeamModulePlugin.groovy for Java or setup.py for Python).
• Once the underlying issue is resolved, I will remove the version exclusion/restriction.
• I will run the SpannerIO integration tests to ensure compatibility with the updated library.

Submit a PR to unpin the dependency.