That's a fair point Tobias. I'll get that merged and cut a new RC. It's important we don't break pyiceberg support.
On Thu, May 21, 2026, 6:17 AM Tobias <[email protected]> wrote: > Hi all, > > -1 (non-binding) > > It looks like a38f57ff5171ff10ebc354992d8d49c253893ccf broke > compatibility with pyiceberg, > https://github.com/apache/iceberg-go/pull/1102 would fix this. > > The field was marked as deprecated/don't write a long time ago, and > pyiceberg rejects reading manifests that contain it. > > Even though this is a gray area, one could argue pyiceberg should not > reject reading it, it's still a regression, previous to this, pyiceberg > could read files produced by iceberg-go, I think we should retain that > compatibility as I also don't see the use of writing distinct_counts. > > Kind regards > Tobias > > Am Mo., 18. Mai 2026 um 23:01 Uhr schrieb Matt Topol < > [email protected]>: > >> Hi, >> >> I would like to propose the following release candidate (RC0) of >> Apache Iceberg Go version v0.6.0. >> >> This release candidate is based on commit: >> 53fa29ccc29817c2238405c50716e8058419ac61 [1] >> >> The source release rc0 is hosted at [2]. >> >> Please download, verify checksums and signatures, run the unit tests, >> and vote on the release. See [3] for how to validate a release candidate. >> >> The vote will be open for at least 72 hours. >> >> [ ] +1 Release this as Apache Iceberg Go v0.6.0 >> [ ] +0 >> [ ] -1 Do not release this as Apache Iceberg Go v0.6.0 because... >> >> [1]: >> https://github.com/apache/iceberg-go/tree/53fa29ccc29817c2238405c50716e8058419ac61 >> [2]: >> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-go-0.6.0-rc0 >> [3]: >> https://github.com/apache/iceberg-go/blob/main/dev/release/README.md#verify >> >
