fafacao86 commented on issue #14980: URL: https://github.com/apache/iceberg/issues/14980#issuecomment-3720197771
> Can't you just delete the table location? Why would you need a special procedure? Yes. I'm planning to do so in my own catalog implementation. But S3 doesn't have a concept like atomic drop directory, it's like two steps: listPrefix then delete a list of files. In between the two steps there might be a concurrent writer producing orphan files under some edge cases. But this is just edge case though. I think I can handle this in my own catalog implementation by keeping an extra mark of a table location is purged and do a recheck later. -- 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]
