vamen opened a new issue, #5607: URL: https://github.com/apache/iceberg/issues/5607
### Feature Request / Improvement though it is rare, but it often happens that spark gets shut down when the iceberg table write is still in progress and dangling lock is left in hive_locks table and subsequent run gets failed because of lock present in hive_lockcs table. I bet this issue happen occasionally in other tables which are used for locking. In such cases we manually unlock the table using hive metastore client. I think it is usefull if we have an api in catalog similar to create table, drop table etc. to unlock the table. Also we have a use case where we read the data from iceberg table modify it and write it back. in this process we don't want other process to write to the same iceberg table. it would be great if lock api is also supported at catalog level so that we can pessimistically lock the iceberg table. ### Query engine _No response_ -- 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]
