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 5be0e27689 [DOCS][MINOR] add File base lock description (#7604)
5be0e27689 is described below
commit 5be0e276899f9af263fa4dbf784c36ab152bb32d
Author: 冯健 <[email protected]>
AuthorDate: Fri Jan 6 18:16:26 2023 +0800
[DOCS][MINOR] add File base lock description (#7604)
Co-authored-by: jian.feng <[email protected]>
---
website/versioned_docs/version-0.12.0/concurrency_control.md | 12 +++++++++++-
website/versioned_docs/version-0.12.1/concurrency_control.md | 12 +++++++++++-
website/versioned_docs/version-0.12.2/concurrency_control.md | 12 +++++++++++-
3 files changed, 33 insertions(+), 3 deletions(-)
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 5e85ee0bed..f8172953f7 100644
--- a/website/versioned_docs/version-0.12.0/concurrency_control.md
+++ b/website/versioned_docs/version-0.12.0/concurrency_control.md
@@ -51,11 +51,21 @@ There are 4 different lock providers that require different
configurations to be
**`FileSystem`** based lock provider
+FileSystem based lock provider provides an out-of-box way to support multiple
writers cross different jobs/applications based on atomic
+create/delete operations of the underlying filesystem
+
```
hoodie.write.lock.provider=org.apache.hudi.client.transaction.lock.FileSystemBasedLockProvider
-hoodie.write.lock.filesystem.path
+hoodie.write.lock.filesystem.path (optional)
+hoodie.write.lock.filesystem.expire (optional)
```
+When using the FileSystem based lock provider, by default, the lock file will
store into `hoodie.base.path`+`/.hoodie/lock`,
+in addition, you can use a custom folder to store the lock file by specify
`hoodie.write.lock.filesystem.path`
+
+In case the lock cannot release during job crash, you can set
`hoodie.write.lock.filesystem.expire`, provide an expiry time in minutes, lock
will never expire as default.
+you can also delete lock file manually in such situation
+
**`Zookeeper`** based lock provider
```
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 5e85ee0bed..f8172953f7 100644
--- a/website/versioned_docs/version-0.12.1/concurrency_control.md
+++ b/website/versioned_docs/version-0.12.1/concurrency_control.md
@@ -51,11 +51,21 @@ There are 4 different lock providers that require different
configurations to be
**`FileSystem`** based lock provider
+FileSystem based lock provider provides an out-of-box way to support multiple
writers cross different jobs/applications based on atomic
+create/delete operations of the underlying filesystem
+
```
hoodie.write.lock.provider=org.apache.hudi.client.transaction.lock.FileSystemBasedLockProvider
-hoodie.write.lock.filesystem.path
+hoodie.write.lock.filesystem.path (optional)
+hoodie.write.lock.filesystem.expire (optional)
```
+When using the FileSystem based lock provider, by default, the lock file will
store into `hoodie.base.path`+`/.hoodie/lock`,
+in addition, you can use a custom folder to store the lock file by specify
`hoodie.write.lock.filesystem.path`
+
+In case the lock cannot release during job crash, you can set
`hoodie.write.lock.filesystem.expire`, provide an expiry time in minutes, lock
will never expire as default.
+you can also delete lock file manually in such situation
+
**`Zookeeper`** based lock provider
```
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 5e85ee0bed..5dcbcfee6b 100644
--- a/website/versioned_docs/version-0.12.2/concurrency_control.md
+++ b/website/versioned_docs/version-0.12.2/concurrency_control.md
@@ -51,11 +51,21 @@ There are 4 different lock providers that require different
configurations to be
**`FileSystem`** based lock provider
+FileSystem based lock provider provides an out-of-box way to support multiple
writers cross different jobs/applications based on atomic
+create/delete operations of the underlying filesystem
+
```
hoodie.write.lock.provider=org.apache.hudi.client.transaction.lock.FileSystemBasedLockProvider
-hoodie.write.lock.filesystem.path
+hoodie.write.lock.filesystem.path (optional)
+hoodie.write.lock.filesystem.expire (optional)
```
+When using the FileSystem based lock provider, by default, the lock file will
store into `hoodie.base.path`+`/.hoodie/lock`,
+in addition, you can use a custom folder to store the lock file by specify
`hoodie.write.lock.filesystem.path`
+
+In case the lock cannot release during job crash, you can set
`hoodie.write.lock.filesystem.expire`, provide an expiry time in minutes, lock
will never expire as default.
+you can also delete lock file manually in such situation
+
**`Zookeeper`** based lock provider
```
