Introduce basic sanity test for MV used by Observability Integrations #995
+635
−0
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.
Description
This PR introduces basic sanity tests for Flint Spark integration. These tests are designed to quickly capture obvious breaking changes in materialized views used by Observability Integration dashboards. The focus is to provide a safeguard against unexpected regressions in key MV functionalities. In the future, Observability Integration will need to maintain a complete set of tests to cover all dimensions, such as supported integrations, raw or aggregate MV etc.
Related Issues
#88
Check List
--signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.