rdblue commented on PR #5327: URL: https://github.com/apache/iceberg/pull/5327#issuecomment-1207478697
@szehon-ho, what I originally meant was that it would be fine for the caller to manually call `dropTable` first. I'm hesitant to add a `force` option because it's basically the same thing as a reset, we just hide it a bit. Thinking about the problem a bit more, I'm not sure that the use cases we're trying to satisfy make this a catalog operation. If this is about replacing the metadata for a single existing table, why not make this a table operation? Or better yet, why not use the existing table operation to do this? If the table exists, then you can always call `table.operations().commit(table.operations().current(), replacementMetadata)`. -- 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]
