This is an automated email from the ASF dual-hosted git repository.
xushiyan pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hudi.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e75acd314e [DOCS][MINOR] Update docs for fs based lock provider (#7587)
e75acd314e is described below
commit e75acd314eb3485cfea7517a4a952364edad50f7
Author: Shiyan Xu <[email protected]>
AuthorDate: Fri Jan 6 01:02:59 2023 +0800
[DOCS][MINOR] Update docs for fs based lock provider (#7587)
---
website/docs/concurrency_control.md | 9 ++++++++-
website/docs/metadata.md | 4 ++--
website/releases/release-0.12.0.md | 6 +++---
website/versioned_docs/version-0.12.0/concurrency_control.md | 9 ++++++++-
website/versioned_docs/version-0.12.0/metadata.md | 4 ++--
website/versioned_docs/version-0.12.1/concurrency_control.md | 9 ++++++++-
website/versioned_docs/version-0.12.1/metadata.md | 4 ++--
website/versioned_docs/version-0.12.2/concurrency_control.md | 9 ++++++++-
website/versioned_docs/version-0.12.2/metadata.md | 4 ++--
9 files changed, 43 insertions(+), 15 deletions(-)
diff --git a/website/docs/concurrency_control.md
b/website/docs/concurrency_control.md
index a784b705f9..5e85ee0bed 100644
--- a/website/docs/concurrency_control.md
+++ b/website/docs/concurrency_control.md
@@ -47,7 +47,14 @@ hoodie.cleaner.policy.failed.writes=LAZY
hoodie.write.lock.provider=<lock-provider-classname>
```
-There are 3 different server based lock providers that require different
configuration to be set.
+There are 4 different lock providers that require different configurations to
be set.
+
+**`FileSystem`** based lock provider
+
+```
+hoodie.write.lock.provider=org.apache.hudi.client.transaction.lock.FileSystemBasedLockProvider
+hoodie.write.lock.filesystem.path
+```
**`Zookeeper`** based lock provider
diff --git a/website/docs/metadata.md b/website/docs/metadata.md
index 75cf3b0e0c..c10d3e0d9b 100644
--- a/website/docs/metadata.md
+++ b/website/docs/metadata.md
@@ -94,5 +94,5 @@ hoodie.cleaner.policy.failed.writes=LAZY
hoodie.write.lock.provider=<distributed-lock-provider-classname>
```
-Note that there are 3 different distributed [lock providers
available](/docs/concurrency_control#enabling-multi-writing)
-to choose from: `ZookeeperBasedLockProvider`,
`HiveMetastoreBasedLockProvider`, and `DynamoDBBasedLockProvider`.
\ No newline at end of file
+Note that there are 4 different [lock providers
available](/docs/concurrency_control#enabling-multi-writing)
+to choose from: `FileSystemBasedLockProvider`, `ZookeeperBasedLockProvider`,
`HiveMetastoreBasedLockProvider`, and `DynamoDBBasedLockProvider`.
\ No newline at end of file
diff --git a/website/releases/release-0.12.0.md
b/website/releases/release-0.12.0.md
index fe764b5dd8..83b6671cbd 100644
--- a/website/releases/release-0.12.0.md
+++ b/website/releases/release-0.12.0.md
@@ -91,12 +91,12 @@ However, if this feature is enabled, restore cannot be
supported. This limitatio
and the development of this feature can be tracked in
[HUDI-4500](https://issues.apache.org/jira/browse/HUDI-4500).
:::
-### Filesystem based Lock Provider
+### File system based Lock Provider
For multiple writers using optimistic concurrency control, Hudi already
supports lock providers based on
-Zookeeper, Hive Metastore or Amazon DynamoDB. In this release, there is a new
filesystem based lock provider. Unlike the
+Zookeeper, Hive Metastore or Amazon DynamoDB. In this release, there is a new
file system based lock provider. Unlike the
need for external systems in other lock providers, this implementation
acquires/releases a lock based on atomic
-create/delete operations of the underlying filesystem. To use this lock
provider, users need to set the following
+create/delete operations of the underlying file system. To use this lock
provider, users need to set the following
minimal configurations (please check the [lock
configuration](/docs/configurations#Locks-Configurations) for a few
other optional configs that can be used):
```
diff --git a/website/versioned_docs/version-0.12.0/concurrency_control.md
b/website/versioned_docs/version-0.12.0/concurrency_control.md
index a784b705f9..5e85ee0bed 100644
--- a/website/versioned_docs/version-0.12.0/concurrency_control.md
+++ b/website/versioned_docs/version-0.12.0/concurrency_control.md
@@ -47,7 +47,14 @@ hoodie.cleaner.policy.failed.writes=LAZY
hoodie.write.lock.provider=<lock-provider-classname>
```
-There are 3 different server based lock providers that require different
configuration to be set.
+There are 4 different lock providers that require different configurations to
be set.
+
+**`FileSystem`** based lock provider
+
+```
+hoodie.write.lock.provider=org.apache.hudi.client.transaction.lock.FileSystemBasedLockProvider
+hoodie.write.lock.filesystem.path
+```
**`Zookeeper`** based lock provider
diff --git a/website/versioned_docs/version-0.12.0/metadata.md
b/website/versioned_docs/version-0.12.0/metadata.md
index 75cf3b0e0c..c10d3e0d9b 100644
--- a/website/versioned_docs/version-0.12.0/metadata.md
+++ b/website/versioned_docs/version-0.12.0/metadata.md
@@ -94,5 +94,5 @@ hoodie.cleaner.policy.failed.writes=LAZY
hoodie.write.lock.provider=<distributed-lock-provider-classname>
```
-Note that there are 3 different distributed [lock providers
available](/docs/concurrency_control#enabling-multi-writing)
-to choose from: `ZookeeperBasedLockProvider`,
`HiveMetastoreBasedLockProvider`, and `DynamoDBBasedLockProvider`.
\ No newline at end of file
+Note that there are 4 different [lock providers
available](/docs/concurrency_control#enabling-multi-writing)
+to choose from: `FileSystemBasedLockProvider`, `ZookeeperBasedLockProvider`,
`HiveMetastoreBasedLockProvider`, and `DynamoDBBasedLockProvider`.
\ No newline at end of file
diff --git a/website/versioned_docs/version-0.12.1/concurrency_control.md
b/website/versioned_docs/version-0.12.1/concurrency_control.md
index a784b705f9..5e85ee0bed 100644
--- a/website/versioned_docs/version-0.12.1/concurrency_control.md
+++ b/website/versioned_docs/version-0.12.1/concurrency_control.md
@@ -47,7 +47,14 @@ hoodie.cleaner.policy.failed.writes=LAZY
hoodie.write.lock.provider=<lock-provider-classname>
```
-There are 3 different server based lock providers that require different
configuration to be set.
+There are 4 different lock providers that require different configurations to
be set.
+
+**`FileSystem`** based lock provider
+
+```
+hoodie.write.lock.provider=org.apache.hudi.client.transaction.lock.FileSystemBasedLockProvider
+hoodie.write.lock.filesystem.path
+```
**`Zookeeper`** based lock provider
diff --git a/website/versioned_docs/version-0.12.1/metadata.md
b/website/versioned_docs/version-0.12.1/metadata.md
index 75cf3b0e0c..c10d3e0d9b 100644
--- a/website/versioned_docs/version-0.12.1/metadata.md
+++ b/website/versioned_docs/version-0.12.1/metadata.md
@@ -94,5 +94,5 @@ hoodie.cleaner.policy.failed.writes=LAZY
hoodie.write.lock.provider=<distributed-lock-provider-classname>
```
-Note that there are 3 different distributed [lock providers
available](/docs/concurrency_control#enabling-multi-writing)
-to choose from: `ZookeeperBasedLockProvider`,
`HiveMetastoreBasedLockProvider`, and `DynamoDBBasedLockProvider`.
\ No newline at end of file
+Note that there are 4 different [lock providers
available](/docs/concurrency_control#enabling-multi-writing)
+to choose from: `FileSystemBasedLockProvider`, `ZookeeperBasedLockProvider`,
`HiveMetastoreBasedLockProvider`, and `DynamoDBBasedLockProvider`.
\ No newline at end of file
diff --git a/website/versioned_docs/version-0.12.2/concurrency_control.md
b/website/versioned_docs/version-0.12.2/concurrency_control.md
index a784b705f9..5e85ee0bed 100644
--- a/website/versioned_docs/version-0.12.2/concurrency_control.md
+++ b/website/versioned_docs/version-0.12.2/concurrency_control.md
@@ -47,7 +47,14 @@ hoodie.cleaner.policy.failed.writes=LAZY
hoodie.write.lock.provider=<lock-provider-classname>
```
-There are 3 different server based lock providers that require different
configuration to be set.
+There are 4 different lock providers that require different configurations to
be set.
+
+**`FileSystem`** based lock provider
+
+```
+hoodie.write.lock.provider=org.apache.hudi.client.transaction.lock.FileSystemBasedLockProvider
+hoodie.write.lock.filesystem.path
+```
**`Zookeeper`** based lock provider
diff --git a/website/versioned_docs/version-0.12.2/metadata.md
b/website/versioned_docs/version-0.12.2/metadata.md
index 75cf3b0e0c..c10d3e0d9b 100644
--- a/website/versioned_docs/version-0.12.2/metadata.md
+++ b/website/versioned_docs/version-0.12.2/metadata.md
@@ -94,5 +94,5 @@ hoodie.cleaner.policy.failed.writes=LAZY
hoodie.write.lock.provider=<distributed-lock-provider-classname>
```
-Note that there are 3 different distributed [lock providers
available](/docs/concurrency_control#enabling-multi-writing)
-to choose from: `ZookeeperBasedLockProvider`,
`HiveMetastoreBasedLockProvider`, and `DynamoDBBasedLockProvider`.
\ No newline at end of file
+Note that there are 4 different [lock providers
available](/docs/concurrency_control#enabling-multi-writing)
+to choose from: `FileSystemBasedLockProvider`, `ZookeeperBasedLockProvider`,
`HiveMetastoreBasedLockProvider`, and `DynamoDBBasedLockProvider`.
\ No newline at end of file
