Releases: elementary-data/dbt-data-reliability
Releases · elementary-data/dbt-data-reliability
0.6.5
What's Changed
- Support dbt utils upgrade by @IDoneShaveIt in #180
- Using
global_min_bucket_start
as themin_metric_time
. by @elongl in #177 - New anomaly tests (
volume_anomalies
,freshness_anomalies
) by @elongl in #158 - Schema changes from baseline (
schema_changes_from_baseline
) by @haritamar in #171 - Support dbt expectations by @IDoneShaveIt in #167
- Elementary full refresh var (
elementary_full_refresh
) by @haritamar in #182 - Added
orchestrator
todbt_invocations
. by @elongl in #185 - fix databricks create table as bug by @IDoneShaveIt in #187
- Add default description to elementary tests by @IDoneShaveIt in #188
- Json schema validation (
json_schema
) by @haritamar in #186 - fix dimension anomalies bug by @IDoneShaveIt in #189
- Handling case in which invocation vars contain non-serializable data. by @elongl in #191
- Installing dbt-utils based on dbt version. by @elongl in #192
- fix surrogate key by @IDoneShaveIt in #194 & #195
New Contributors
Full Changelog: 0.6.4...0.6.5
0.6.4
What's Changed
- Getting the actual version rather than the one specified in packages.yml by @elongl in #166
- Added jobs to
dbt_invocations
and create thejob_run_results
view by @elongl in #161 - Checking that Elementary is enabled prior to materializing. by @elongl in #170
- Auto-casting 'True' and 'False' to booleans. by @elongl in #169
Please note: If you were using any of the disablement vars (disable_*
) with a Jinja expression (most notably target.name != prod
) rather than true
or false
- up until now, it would've always been disabled regardless of the expression.
In this release, the expression is taken into account upon deciding whether to disable or not.
Full Changelog: 0.6.3...0.6.4
0.6.3
0.6.2
Bug Fixes
Fixed a bug where alerts use test name instead of test short name
0.6.1
Bug Fixes
Fixed a bug to support older dbt-snowflake adapter versions 😱
0.6.0
What's Changed
- Storing tests' results samples within
elementary_test_results
to improve report's generation time by @elongl in #134 - Caching the artifacts so that it only uploads on changes by @elongl in #131
- remove
compiled_code
fromdbt_tests
by @nzewail in #140 - Fixed a bug that caused uploading the dbt invocation to crash by @elongl in #139 and #150
- Test tables are stored by default in the Elementary schema rather than a separate tests schema by @haritamar in #141
- Added a flag of whether the invocation was the first or last of the day to
model_run_results
by @eKatia in #144 - Added documentation to
dbt_invocations
by @smitsrr in #147 - Writing an indicate error message when a relation doesn't exist in the anomaly tests. by @elongl in #148
- Added support for dbt's custom test names in
elementary_test_results
by @IDoneShaveIt in #137 - Added query ID to
dbt_run_results
,model_run_results
, andsnapshot_run_results
by @kkprab in #146 - Reduced max query size on BigQuery by @elongl in #155
New Contributors
- @nzewail made their first contribution in #140
- @haritamar made their first contribution in #141
- @smitsrr made their first contribution in #147
- @kkprab made their first contribution in #146
Full Changelog: 0.5.5...0.6.0
0.5.5
New Features
- Added selectors, invocation vars, threads and target details to
dbt_invocations
table - Added new indexes and invocation flags (is first/last invocation of the day) to
model_run_results
view - Thanks @eKatia for her contribution!!!
Changes
- Removed
seleceted_resources
column fromdbt_invocations
table to fix "value too long" bug
0.5.4
New Features
- Added
dbt_invocations
table that tracks run times, command, vars, selected_resources, dbt and Elementary versions 💯 ✌🏻
Changes
- Artifacts are uploaded at on-run-end hooks to keep up-to-date and avoid inconsistency with alerts and report's data 💪🏻
- Change raw data insertion mechanism (artifacts, run results, test results, etc)
0.5.3
Fixed a bug in which certain macros were not implemented on certain adapters.