kevinjqliu opened a new issue, #1200: URL: https://github.com/apache/iceberg-go/issues/1200
Follow up to #915, relates to #1199 Users can see different Go value types for the same logical `day(...)` partition value depending on how a manifest encoded it in Avro. On current `main` (`1e4916f`), this is reproducible: - `day(...)` encoded as Avro `int` with `logicalType: date` reads as `iceberg.Date(19000)` - the same `day(...)` value encoded as legacy plain Avro `int` reads as `int32(19000)` Both encodings represent days since `1970-01-01`, so iceberg-go should not leak that Avro encoding difference to users. When reading manifests, `day(...)` partition values should consistently be exposed as Iceberg `Date`. This should only apply to fields whose partition spec transform is `day(...)`; other plain integer partition values should remain integers. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
