kbendick commented on issue #3541:
URL: https://github.com/apache/iceberg/issues/3541#issuecomment-972480717


   Spark has access to that information, but presently it just throws an 
exception after doing the lists.
   
   So if it was changed on the spark side to list the tables and drop them if 
`cascade` is used, Iceberg wouldn't need to know at all.
   
   But unfortunately that's not what Spark does. I'll try syncing up with some 
folks that are more deeply integrated with the core Spark community to see if 
something can be done, but I'm not super confident much will come from it. At 
least not very quickly.
   


-- 
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]

Reply via email to