Vitaly Terentyev
Vitaly Terentyev
@ahmedabu98 Could you please take a look at the failed Iceberg checks? I'm not sure why they fail here and succeed on master.
`[ERROR] Failures: 2025-12-10T10:30:07.3944492Z [ERROR] PubSubToBigQueryYamlIT.testPubSubToBigQuery:88->basePubSubToBigQuery:139 value of : result.check if meets all conditions 2025-12-10T10:30:07.3945454Z expected : CONDITION_MET 2025-12-10T10:30:07.3945794Z but was : TIMEOUT`
`|[v2/sourcedb-to-spanner/target/surefire-reports/TEST-com.google.cloud.teleport.v2.templates.CassandraAllDataTypesIT.xml](#user-content-r39)||1 ❌||803s|`
> `|[v2/sourcedb-to-spanner/target/surefire-reports/TEST-com.google.cloud.teleport.v2.templates.CassandraAllDataTypesIT.xml](#user-content-r39)||1 ❌||803s|` This appeared after the rebase, so I don't think the RC is the cause.
[Bug]: Add SchemaFieldNumber annotations to Iceberg to prevent potential update compatibility issues
> There are several more places we need to add 'SchemaFieldNumber's to fix update compatibility for IcebergIO. Opened [#37055](https://github.com/apache/beam/pull/37055) for this. > > cc: [@shunping](https://github.com/shunping) in case this can be...
> Looking at failures: > > * [PreCommit Java ElasticSearch IO Direct](https://github.com/apache/beam/actions/runs/20040634643/job/57521862000?pr=37050) - failing because of [[Elasticsearch] Add support for v9.x #36670](https://github.com/apache/beam/pull/36670) which changed the workflow, but didn't make it...
> > > @shunping please follow go/beam-release#during-release to publish Dataflow containers > > > > > > ACK. Working on this right now. > > The dataflow containers for rc2...