Davis-Zhang-Onehouse opened a new pull request, #11667: URL: https://github.com/apache/hudi/pull/11667
OSS jira: https://issues.apache.org/jira/browse/HUDI-8005 OSS PR: https://github.com/apache/hudi/compare/master...Davis-Zhang-Onehouse:hudi-oss:hudi-8005 The change adds a new lock provider which is exactly the same as existing dynamoDB based one except the way the partition key part is handled. Existing one: The parameter is explicitly specified in lock configuration. New one: It is implicitly derived from the hudi table base path and hudi table name. The 2 attributes are available in todays lockConfig, which contains all props from hudiWriterConfig. Test: Unit test and integration 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. ### Contributor's checklist - [ ] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [ ] Change Logs and Impact were stated clearly - [ ] Adequate tests were added if applicable - [ ] CI passed -- 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]
