[HUDI-6395]Scheduling jobs should not fail when there is no scheduled compaction or clustering plan#9002
Closed
wkang13579 wants to merge 7 commits intoapache:masterfrom
wkang13579:HUDI-6395
Closed
[HUDI-6395]Scheduling jobs should not fail when there is no scheduled compaction or clustering plan#9002wkang13579 wants to merge 7 commits intoapache:masterfrom wkang13579:HUDI-6395
wkang13579 wants to merge 7 commits intoapache:masterfrom
wkang13579:HUDI-6395
Conversation
… compaction or clustering plan
Collaborator
danny0405
reviewed
Jun 18, 2023
| throw new HoodieClusteringException("There is no scheduled clustering in the table."); | ||
| LOG.info("There is no scheduled clustering in the table."); | ||
| return 0; | ||
| } |
Contributor
There was a problem hiding this comment.
can we fix the test faliues
… compaction or clustering plan
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.
Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change
ticket number here and follow the instruction to make
changes to the website.
Contributor's checklist