Skip to content

Latest commit

 

History

History
190 lines (114 loc) · 8.03 KB

CHANGELOG.md

File metadata and controls

190 lines (114 loc) · 8.03 KB

dbt-expectations v0.5.4

New Features

  • Adds test for column presence by @rcaddell in calogica#149

Fixes

  • Fix emails.sql by @clausherther in calogica#153
  • Fix expect_row_values_to_have_recent_data issues on bigquery by @clausherther in calogica#147

New Contributors

dbt-expectations v0.5.3

New Features

  • Add group_by parameter to expect_column_values_to_be_increasing and expect_column_values_to_be_decreasing (#146 @Lucasthenoob)

dbt-expectations v0.5.2

Fixes

  • Fix expect_row_values_to_have_recent_data to use current timestamp by @MrJoosh in calogica#145 (also fixes calogica#104)

New Features

  • Add new expect_column_values_to_have_consistent_casing test by @agusfigueroa-htg in calogica#138

Doc Updates 💌

  • Update README.md by @kdw2126 in calogica#134
  • Fix documentation to note DBT 1.0.0 compatibility by @kdw2126 in calogica#136

New Contributors

dbt-expectations v0.5.1

Fixes

  • Add better support for Redshift by typing implicit varchar fields explicitly to strings. (#131 #132)

dbt-expectations v0.5.0

  • adds full support for dbt 1.x without backwards compatability
  • supports dbt-date 0.5.0, which supports dbt-utils 0.8.0

dbt-expectations v0.4.7

  • Patch: adds support for dbt 1.x

dbt-expectations v0.4.6

What's Changed

  • Append missing optional parameters documentation to README.md by @makotonium in calogica#124
  • Fix missing group_by default value in string_matching macros by @samantha-guerriero-cko in calogica#126

New Contributors

  • @makotonium made their first contribution in calogica#124
  • @samantha-guerriero-cko made their first contribution in calogica#126

dbt-expectations v0.4.5

Fixes

Doc Updates

  • Append missing optional parameters documentation to README.md (#124 by @makotonium)

dbt-expectations v0.4.5

Features

  • Add an optional argument to allow for intervals of date_part in expect_row_values_to_have_data_for_every_n_datepart. (#110 by @lewisarmistead)

Fixes

  • Fixed a regression introduced in 0.4.3 that made expect_table_columns_to_match_ordered_list incomatible with Redshift (#123 by @mirosval)

dbt-expectations v0.4.4

Fixes

  • Replaced hardcoded value in expect_column_to_exist with mapping call to provided transform filter and join to reduce list back to single value. (#118 @UselessAlias)

dbt-expectations v0.4.3

Fixes

  • Fixes incompatibility on Snowflake with use of row_number() without order by in expect_table_columns_to_match_ordered_list(#112)

Features

Under the hood

  • Supports dbt 0.21.x

dbt-expectations v0.4.2

Features

  • Added row_condition to expect_grouped_row_values_to_have_recent_data and expect_row_values_to_have_recent_data to allow for partition filtering before applying the recency test (#106 w/ @edbizarro)

Under the hood

  • Converted Jinja set logic to SQL joins to make it easier to follow and iterate in the future (#108)

dbt-expectations v0.4.1

Fixes

  • expect_table_columns_to_match_list remove '' to leave columns as numbers (#98)

  • expect_table_columns_to_match_ordered_list now explicitly casts the column list to a string type (#99)

  • Fixes regex matching tests for Redshift by adding a Redshift specific adapter macro in regexp_instr (#99 @mirosval)

dbt-expectations v0.4.0

Breaking Changes

  • Requires dbt >= 0.20

  • Requires dbt-date >= 0.4.0

  • Updates test macros to tests to support dbt >= 0.20

  • Updates calls to adapter.dispatch to support dbt >= 0.20 (see Changes to dispatch in dbt v0.20 #78)

dbt-expectations v0.3.7

  • Fix join in expect_column_values_to_be_in_set (#91 @ahmedrad)
  • Add support for Redshift random function in rand macro (#92 @ahmedrad)

dbt-expectations v0.3.6

  • Remove unnecessary macro to fix issue with 0.19.2 (#88)

dbt-expectations v0.3.5

Features

  • Added a new macro, expect_row_values_to_have_data_for_every_n_datepart, which tests whether a model has values for every grouped date_part.

    For example, this tests whether a model has data for every day (grouped on date_col) from either a specified start_date and end_date, or for the min/max value of the specified date_col.

    tests:
        - dbt_expectations.expect_row_values_to_have_data_for_every_n_datepart:
            date_col: date_day
            date_part: day

Fixes

dbt-expectations v0.3.4

Features

  • Added support for optional min_value and max_value parameters to all*_between_* tests. (#70)

  • Added support for strictly parameter to between tests. If set to True, striclty changes the operators >= and <= to> and <.

    For example, while

    dbt_expectations.expect_column_stdev_to_be_between:
        min_value: 0

    evaluates to >= 0,

    dbt_expectations.expect_column_stdev_to_be_between:
        min_value: 0
        strictly: True

    evaluates to > 0. (#72, #74)

Fixes

  • Corrected a typo in the README (#67)

Under the hood

  • Refactored get_select function to generate SQL grouping more explicitly (#63))

  • Added dispatch call to expect_table_row_count_to_equal to make it easier to shim macros for the tsql-utils package (#64 Thanks @alieus!)