BjornPrime opened a new issue, #27326: URL: https://github.com/apache/beam/issues/27326
### What needs to happen? The current implementation of GCSIO uses an internal field (batch._responses) from the GCS client. This are unlikely to be updated but still is potentially subject to change so the version has an upper limit set to avoid breakages. Please check if a new version of the [GCS client](https://github.com/googleapis/python-storage) has been released and increment the version in setup.py if it's compatible. We can consider to close this issue when either condition is met: - Beam vendors the GCS client. - GCS client is updated to allow support for our use case without reference to internal methods. - GCSIO is switched to relying on another client. Until then, don't close this issue, instead, move it to the next release milestone after updating the version in https://github.com/apache/beam/blob/master/sdks/python/setup.py ### Issue Priority Priority: 3 (nice-to-have improvement) ### Issue Components - [X] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
