lirui-apache opened a new issue, #10006:
URL: https://github.com/apache/iceberg/issues/10006

   ### Apache Iceberg version
   
   main (development)
   
   ### Query engine
   
   None
   
   ### Please describe the bug 🐞
   
   When `HiveTableOperations` commits, which kind of `HiveLock` to use is 
decided using the new table metadata: 
https://github.com/apache/iceberg/blob/main/hive-metastore/src/main/java/org/apache/iceberg/hive/HiveTableOperations.java#L180
   
   Suppose a table was initially created with lock enabled. At some time, we 
decide to disable the lock by running an ALTER TABLE to change the property. I 
wonder if this ALTER TABLE can cause problem with other concurrent writes, 
because they will use different lock mechanism.


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

Reply via email to