nsivabalan opened a new pull request, #6854:
URL: https://github.com/apache/hudi/pull/6854
### Change Logs
With Hudi's OCC, one of the commit is expected to fail if there are
overalapping writes. From a user's standpoint, very likely user may retry the
failed write w/o any additional action. So, adding a retry functionality to
spark datasource writes with hudi automatically incase of conflict failures.
### Impact
User experience w/ multi-writers will be improved with these automatic
retries.
**Risk level: medium **
Users should enable the retries w/ caution since it could keep retrying the
failed commit again until max retries are exhausted. Could result in some
compute cost for large batches.
### Documentation Update
_Describe any necessary documentation update if there is any new feature,
config, or user-facing change_
- Configs introduced
- `hoodie.write.lock.retry.on.conflict.failures` : to enable retries on
conflict failures. Default is false.
- `hoodie.write.lock.num.retries.on.conflict.failures` : max number of
times to retry on conflict failures.
- _Any new feature or user-facing change requires updating the Hudi website.
Please create a Jira ticket, attach the
ticket number here and follow the
[instruction](https://hudi.apache.org/contribute/developer-setup#website) to
make
changes to the website._
### 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]
