Davis Zhang created HUDI-8090:
---------------------------------
Summary: New zookeeper based lock provider
Key: HUDI-8090
URL: https://issues.apache.org/jira/browse/HUDI-8090
Project: Apache Hudi
Issue Type: Improvement
Reporter: Davis Zhang
Add a new lock provider which is exactly the same as existing zookeeper based
one except the way the partition key part is handled. To be specific:
* It requiresTable name as indicated by "hoodie.table.name".
* It requiresTable base path "hoodie.base.path".
* The zookeeper base path key
([hoodie.write.lock.dynamodb.partition_key|https://hudi.apache.org/docs/configurations/#hoodiewritelockdynamodbpartition_key])
is automatically derived as /tmp/{{{}<table name>-<hash of the table base
path>{}}}. To check the exact value, please check relevant log from classÂ
org.apache.hudi.client.transaction.lock.ZookeeperBasedImplicitBasePathLockProvider.
* It will ignore value set by`
hoodie.write.lock.zookeeper.base_path` and
`hoodie.write.lock.zookeeper.lock_key`.
Test:
Unit test
h3. Change Logs
Add new lock provider implementation. For code shared by the new-old lock
provider, they are extracted to a base class.
Unit test + integration test
h3. Impact
None.
h3. Risk level (write none, low medium or high below)
no risk as of now since no one is using the new lock provider.
h3. Documentation Update
In [https://hudi.apache.org/docs/concurrency_control/], we need to add
description for the newly added lock provider.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
