You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "dentiny (via GitHub)" <gi...@apache.org> on 2025/04/29 03:27:05 UTC
[D] [Question] `drop_namespace` behavior inconsistent for different catalogs [iceberg-rust]
GitHub user dentiny created 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 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? 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-unsubscribe@iceberg.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [D] [Question] `drop_namespace` behavior inconsistent for different catalogs [iceberg-rust]
Posted by "liurenjie1024 (via GitHub)" <gi...@apache.org>.
GitHub user liurenjie1024 added a comment to the discussion: [Question] `drop_namespace` behavior inconsistent for different catalogs
This seems to be a common problem also in java/python implementation, and there is no clear answer to that. Personally I think it's reasoanble to unify behaviors.
GitHub link: https://github.com/apache/iceberg-rust/discussions/1274#discussioncomment-12976860
----
This is an automatically sent email for issues@iceberg.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@iceberg.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [D] [Question] `drop_namespace` behavior inconsistent for different catalogs [iceberg-rust]
Posted by "liurenjie1024 (via GitHub)" <gi...@apache.org>.
GitHub user liurenjie1024 added a comment to the discussion: [Question] `drop_namespace` behavior inconsistent for different catalogs
There was some issue there: https://github.com/apache/iceberg-rust/issues/519
GitHub link: https://github.com/apache/iceberg-rust/discussions/1274#discussioncomment-12976923
----
This is an automatically sent email for issues@iceberg.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@iceberg.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [D] [Question] `drop_namespace` behavior inconsistent for different catalogs [iceberg-rust]
Posted by "dentiny (via GitHub)" <gi...@apache.org>.
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-unsubscribe@iceberg.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [D] [Question] `drop_namespace` behavior inconsistent for different catalogs [iceberg-rust]
Posted by "dentiny (via GitHub)" <gi...@apache.org>.
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? 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-unsubscribe@iceberg.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [D] [Question] `drop_namespace` behavior inconsistent for different catalogs [iceberg-rust]
Posted by "dentiny (via GitHub)" <gi...@apache.org>.
GitHub user dentiny added a comment to the discussion: [Question] `drop_namespace` behavior inconsistent for different catalogs
Thanks! It would be nice if you or others who are senior in iceberg field to help consolidate the behavior to reduce confusion :)
GitHub link: https://github.com/apache/iceberg-rust/discussions/1274#discussioncomment-12976950
----
This is an automatically sent email for issues@iceberg.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@iceberg.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [D] [Question] `drop_namespace` behavior inconsistent for different catalogs [iceberg-rust]
Posted by "dentiny (via GitHub)" <gi...@apache.org>.
GitHub user dentiny added a comment to the discussion: [Question] `drop_namespace` behavior inconsistent for different catalogs
Another benefit is we could share tests among catalogs right now they are scattered around
GitHub link: https://github.com/apache/iceberg-rust/discussions/1274#discussioncomment-12976900
----
This is an automatically sent email for issues@iceberg.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@iceberg.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org