Davis-Zhang-Onehouse opened a new pull request, #11790: URL: https://github.com/apache/hudi/pull/11790
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 # 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 # Impact None. # Risk level (write none, low medium or high below) no risk as of now since no one is using the new lock provider. # Documentation Update In https://hudi.apache.org/docs/concurrency_control/, we need to add description for the newly added lock provider. -- 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]
