[HUDI-3686] Fix inline and async table service check in HoodieWriteConfig#5307
Merged
nsivabalan merged 1 commit intoapache:masterfrom Apr 13, 2022
Merged
Conversation
Collaborator
nsivabalan
approved these changes
Apr 13, 2022
Contributor
|
@yihua : this has to go into RC2 right ? |
xushiyan
pushed a commit
that referenced
this pull request
Apr 14, 2022
Contributor
Author
Forgot to reply. It is in RC2. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of the pull request
This PR fixes the check of inline and async table services in
HoodieWriteConfig. This addresses the comment from #4406 .Brief change log
areAnyTableServicesExecutedInline()andareAnyTableServicesAsync()inHoodieWriteConfig.Verify this pull request
This pull request is already covered by existing tests and adds a new test around all async table service configs.
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.