s-sanjay opened a new issue, #14237: URL: https://github.com/apache/iceberg/issues/14237
## Describe the bug When creating a new table in Hive, the `HIVE_LOCK_ENABLED` table property is not respected during table creation. The lock type incorrectly falls back to configuration defaults instead of using the table's metadata properties passed via SQL. ## To Reproduce 1. Create a new Iceberg table with `HIVE_LOCK_ENABLED=false` property 2. Observe that the lock type still uses configuration defaults instead of the specified property ## Expected behavior The lock type should respect the `HIVE_LOCK_ENABLED` property specified in the table's metadata during creation. ## Root Cause PR #10016 changed `lockObject()` to use `base` metadata for lock decisions. However, when creating a new table, `base` is `null`, which causes the lock decision to fall back to configuration defaults instead of using the table's properties. ## Additional context Fixed in PR #14236 -- 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]
