RussellSpitzer commented on PR #6786: URL: https://github.com/apache/iceberg/pull/6786#issuecomment-1424278602
> > So I think either this is a Catalog API or we just have this as part of the "drop table" behavior. > > We already have a catalog-specific API. Which is `catalog.dropTable(identifier, purge=false)` this procedure is just calling that. > > "Drop table" SQL also already has purge and without purge syntax. But without purge will still look up the table due to spark integration (callstack mentioned in the issue #6785). Hence, user cannot use it and need the same functionality from SQL. This is what i'm saying, if we want an api which does not treat it as an Iceberg table first I think we need that as a Catalog API. If Drop Table needs the table to be an iceberg table to drop then I think we either need a new api, or a flag like "force" which attempts to drop the table even if there is an exception. -- 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-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
