Kurtiscwright commented on PR #17918: URL: https://github.com/apache/iceberg/pull/17918#issuecomment-6208995297
> @Kurtiscwright This can't be addressed at the type-definition level. Ownership and maintenance is a responsibility of the Catalog and who runts the maintenance procedure. The catalog should protect data access from secondary references trying to delete, but it's not a property of the type. @danielcweeks I tried to stay away from the terminology Ownership because our community sync discussions made it clear that term invokes a lot of extra requirements outside the Specification scope of a data type. I do think it's in Specification scope to have a well defined field, so it's cross catalog and cross engine, that can be used by a Maintenance operation to guide the correct decision on orphan clean up. I think this should be in the type definition because each entry in a table could be different, meaning in one row the file type could be something maintenance cleans up while the next is a file reference stored in multiple tables. Separately I don't think it's a safe assumption that a table will mostly or only have files co-located/relative with a table. Especially with S3 Buckets being global. -- 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]
