GitHub user dentiny edited a discussion: [Question] `drop_namespace` behavior inconsistent for different catalogs
When checking `drop_namespace` implementation, I found different catalogs doesn't conform to the same behavior. For example, when we delete parent namespace, what would happen to the children namespaces? - memory catalog and s3 table catalog delete children catalog as well - while sql catalog doesn't touch children catalogs I understand the reason behind: - For storage backend which support "directory"-like structure, it makes sense (and is easier) to clean them up all together; - While for object-oriented backend, it's expensive to recursively traverse down to the leaf namespace. I would like to know, if the team think it's ok to specify clearly in the documentation on the behavior? Or it's better to leave it as it as, meaning, all undocumented behavior are undefined and implementation-dependent. Thank you! GitHub link: https://github.com/apache/iceberg-rust/discussions/1274 ---- This is an automatically sent email for issues@iceberg.apache.org. To unsubscribe, please send an email to: issues-unsubscr...@iceberg.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
