fallintoplace commented on issue #1091: URL: https://github.com/apache/iceberg-go/issues/1091#issuecomment-4481563862
I think the minimal fix is to make strict null handling conservative for nullable fields. If the schema field is required, missing null counts can still be treated as no nulls. For optional fields, a missing `null_value_counts` entry should mean unknown / may contain nulls. A focused regression test could build a mock data file with lower/upper bounds present, no null-count entry for a nullable field, and assert that strict evaluation for `id > 0` returns false. -- 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]
