kbendick edited a comment on issue #3541: URL: https://github.com/apache/iceberg/issues/3541#issuecomment-972466345
Yeah. That's what I mean. I know the Spark docs mention it, but they're actually the ones that even throw the exception. I did a pretty deep dive and I can see how Hive tables are able to handle it. They follow an older pathway `DropDatabaseCommand`, which relies on HMS to handle the Cascade. The problem with the approach that you mentioned is that we still wouldn't have the ability to get the `CASCADE` information from the query. Just setting it to `true` by default is most likely not going to work for most cases. It's just not exposed in the interface that Spark provides to external catalog developers. We'd have to implement our own antlr grammar to catch `drop table ... cascade`. That's something that could be done, but it's not a trivial amount of work necessarily. -- 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]
