This is an automated email from the ASF dual-hosted git repository.
kevinjqliu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iceberg.git
The following commit(s) were added to refs/heads/main by this push:
new eb460a524f Docs: Add HadoopTables lock configuration to Hadoop
configuration section (#15520)
eb460a524f is described below
commit eb460a524f3a192e3584a3bdabcff237c38b04a4
Author: Anshul Baliga <[email protected]>
AuthorDate: Tue Mar 17 09:04:12 2026 +0530
Docs: Add HadoopTables lock configuration to Hadoop configuration section
(#15520)
---
docs/docs/configuration.md | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/docs/docs/configuration.md b/docs/docs/configuration.md
index 00e8ed8373..f12bcea6af 100644
--- a/docs/docs/configuration.md
+++ b/docs/docs/configuration.md
@@ -216,6 +216,15 @@ Here are the catalog properties related to locking. They
are used by some catalo
## Hadoop configuration
+### HadoopTables Lock Configuration
+
+When using `HadoopTables` (tables without a catalog), lock properties from the
[Lock catalog properties](#lock-catalog-properties) section can be configured
by prefixing them with `iceberg.tables.hadoop.`. This ensures atomic commits on
file systems like S3 that lack native write mutual exclusion.
+
+!!! info
+ To use DynamoDB as a lock manager with `HadoopTables`, set
`iceberg.tables.hadoop.lock-impl` to
`org.apache.iceberg.aws.dynamodb.DynamoDbLockManager` and
`iceberg.tables.hadoop.lock.table` to your DynamoDB table name. See [DynamoDB
Lock Manager](aws.md#dynamodb-lock-manager) for more details.
+
+### Hive Metastore Configuration
+
The following properties from the Hadoop configuration are used by the Hive
Metastore connector.
The HMS table locking is a 2-step process:
