Hi all, I propose to clarify our delete counts handling in partition stats. We have the following metrics that are marked as optional:
- position_delete_record_count - position_delete_file_count - equality_delete_record_count - equality_delete_file_count If I remember correctly, the reasoning behind this was that tables may have no deletes, hence the counts are optional. The problem is that it creates confusion for readers. Does null mean unknown or absent? I propose we clarify that no counts means 0 for V1/V2 tables in the spec (this is the current behavior in the Java implementation) and make the counts required in V3. What does everybody think? - Anton
