Kenn Knowles
Kenn Knowles
`git log --oneline ^v2.54.0 v2.55.0 -- sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/` yields many changes ``` 5d89a331647 Fixes an upgrade imcompatiblity of BQ read/write transforms (#30562) b6301b52058 fix: support reading arrays of structs from bigquery...
IIRC the above analysis suggested we should keep the scope of the issue at "BigQuery Write" as we have not narrowed it any further.
Also perma-red
Last success 8 months ago? https://github.com/apache/beam/actions/workflows/beam_PerformanceTests_xlang_KafkaIO_Python.yml?query=branch%3Amaster+is%3Asuccess
Should this be run at all?
While bisecting for a good checker version for Beam, confirmed that this also occurs in checker 3.40.0
In case it helps, I am working through the upgrade on https://github.com/apache/beam/pull/29961. Some files are excluded due to crashes and others I am modifying for the enhanced strictness.
Could it make sense to associate a state machine with a class and validate w.r.t. to that instead of the default constructor-initiated state machine? Beam has adopted some annotation-driven APIs...
Agree, keep it sticky.
Bringing over some context from https://cloud.google.com/storage/docs/transcoding it seems like there are the following consistent situations: 1. GCS transcodes and Beam works with this transparently. - `Content-encoding: gzip` - `Content-type: X`...