Hi everyone, I'm cancelling the vote on 1.2.1 RC1.
The hudi-trino connector in RC1 is built against Trino 483, but it does not work on the next Trino (484-SNAPSHOT), which the Trino-side shim that consumes this artifact is built against. Two problems show up there: - With Trino's file system cache enabled, every cached read fails with a ClassCastException, because the connector's cache key provider implements the Trino 483 contract. - Newer Trino bundles Avro 1.12.2, which rejects Hudi's generated Avro classes when reading commit metadata. Both are fixed on release-1.2.1: - https://github.com/apache/hudi/pull/19956 resolves nested Avro records by class - https://github.com/apache/hudi/pull/19985 stops binding HudiCacheKeyProvider on 1.2.1, so Trino's default provider is used With both fixes, the connector built at Trino 483 passes the full Trino E2E suite (31 of 31) against Trino master with caching enabled: https://github.com/voonhous/hudi/actions/runs/35219664987 I'll drop the RC1 staging repository and start a vote on RC2 once CI on the release branch passes. Thanks, Voon
