freshness_anomalies
- monitors anomalies in the frequency of updates. Imagine a table that is being updated hourly and then all of a sudden this table wasn’t updated for 4 hours. Here you would probably use the updated_at
/inserted_at
column as an input for this test.event_freshness_anomalies
- monitors that the underlying data is up to date. Imagine an events table that is being updated hourly correctly but the events themselves are coming with a delay of 2 days from your production databases. Here, you would probably use the event_timestamp
column as an input for this test.--s3-endpoint-url TEXT
).schema_changes_from_baseline
test comparison to be case-insensitive. Thanks Manish Ramrakhiani for bringing this up!TestRunSchema.test_runs: None is not an allowed value error
).where_expression
was only implemented when a timestamp was defined. Thanks Ran Tibi for bringing this up!UnicodeDecodeError
error in Windows due to their default encoding.