JFinis opened a new issue, #9739: URL: https://github.com/apache/iceberg/issues/9739
### Apache Iceberg version None ### Query engine None ### Please describe the bug 🐞 The spec is inconsistent with respect to the `partition_spec_id` column. Here the spec notes: > required | required | 502 partition_spec_id | int | ID of a partition spec used to write the manifest; must be listed in table metadata partition-specs Note that this column is **required** in both v1 and v2. Now, let's have a look at the definition of "table metadata partition-specs": > optional | required | partition-specs | A list of partition specs, stored as full partition spec objects. As we see, `partition-specs` is actually optional in v1. But given that `partition_spec_id` is required in v1 and its contents *must be* listed in the table's `partition-specs`, there is no way that `partition-specs` can be optional. If it was missing, the Iceberg would be ill-formed, as there would be no way for the values in `partition_spec_id` to refer to the missing `partition-specs`. So something is off here. If I see it correctly, there are two remediations: * Define `partition-specs` to be required in v1. Any v1 Iceberg without this field would then be ill-formed. * Loosen the requirement that the values in `partition_spec_id` have to refer to specs in `partitition-specs`. Define what the value is supposed to be (or define that any arbitrary values are allowed) in case of `partition-specs` being absent. -- 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: issues-unsubscr...@iceberg.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
