You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2022/08/01 18:31:04 UTC

[GitHub] [iceberg] rdblue commented on pull request #5327: Support resetTable procedure

rdblue commented on PR #5327:
URL: https://github.com/apache/iceberg/pull/5327#issuecomment-1201564797

   > How about reuse registerTable procedure?
   
   If you mean to add more arguments to `registerTable` so that it is an atomic operation, I don't really see much point to it. If this is a recovery operation for cases like the ones @szehon-ho listed in the issues, then why does it need to be atomic? The table is already broken.
   
   We added `registerTable` as a way to migrate to a new metastore. At the time, there were concerns about people misusing it to fork tables and do other unreliable things. I still have that concern for this operation. Reusing `registerTable` as-is seems like the best way to avoid those problems.


-- 
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-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org