hashmapinc / hashmapinc/Tempus
Data Quality issue should be created in case of no incoming data
Open
bug
Current Iteration
Sprint 8
- Dominant language
- Java
- Stars
- 32
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
In the current implementation if the Data flow stops at the Tempus broker then there is no alert for Data Quality (Frequency)
The Tag presence check should not be present since the frequency of Data points is checked based on the Tags, so a separate Tag presence check is not needed.
Use configured time window for frequency check instead of calculating it from the received data.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.