Add skipping alert functionality #29
Merged
Conversation
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
menishmueli
approved these changes
May 21, 2025
|
|
|
Hi @zemin-piao, tested it and the PR looks good. |
zemin-piao
force-pushed
the
add-skipping-alert-functionality
branch
from
43ffdc3 to
2daa1c0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add skipping alert functionality
Context
There is a need to customize the alerts that we want to enable for different spark jobs. e.g. in certain open table formats, the "filter too long" alert will be raised however because of verbosity of the filtering logic from the additional open table format.
Solution
Added
spark.dataflint.alert.disabledspark configuration for supporting a comma-separated list of alert names, by which alerts won't be shown in the UI.