manojpec opened a new pull request #4114:
URL: https://github.com/apache/hudi/pull/4114
## What is the purpose of the pull request
- Across upgrades, metadata table may have to be re-bootstrapped from the
data table. Usually it is detected by the first write client, and the
metadata table is fully removed and attempt is made to bootstrap. This
bootstrapping is deferred if there are pending actions on the timeline
and until they are resolved.
- Today, spark write client gets the metadata writer for every write.
The metadata writer initialization attempt is made only once to avoid
on the expensive fs exists check on every write path. If the metadata
bootstrapping fails in the first time due to pending actions (which is
usually the case after upgrade), the writer client never tries to
recreate it again, leading to it not updating the metadata table even
after bootstrapping by other writers.
- Fix is to retry metadata table creation until it is successful by
either its own bootstrapping or from the concurrent table services or
other writers
## Brief change log
*(for example:)*
- *Modify AnnotationLocation checkstyle rule in checkstyle.xml*
## Verify this pull request
*(Please pick either of the following options)*
This pull request is a trivial rework / code cleanup without any test
coverage.
*(or)*
This pull request is already covered by existing tests, such as *(please
describe tests)*.
(or)
This change added tests and can be verified as follows:
*(example:)*
- *Added integration tests for end-to-end.*
- *Added HoodieClientWriteTest to verify the change.*
- *Manually verified the change by running a job locally.*
## Committer checklist
- [ ] Has a corresponding JIRA in PR title & commit
- [ ] Commit message is descriptive of the change
- [ ] CI is green
- [ ] Necessary doc changes done or have another open PR
- [ ] For large changes, please consider breaking it into sub-tasks under
an umbrella JIRA.
--
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]
