PR #19 includes the following updates:
- Cast
activity_timestamp
instg_mailchimp__campaign_activities
andsend_timestamp
instg_mailchimp__campaigns
todbt.type_timestamp()
. This ensures thedbt.datediff()
function in themailchimp__campaign_activities
model in thedbt_mailchimp
package properly runs in Redshift. - Corrected source freshness variables to properly reference
mailchimp_using_automations
.
- Updated the source freshness test enablement/disablement to leverage the dbt-core
config: enabled:
architecture. - Added source freshness tests for models utilizing the
mailchimp_using_segments
variable.
- Updated the pull request templates.
- Included auto-releaser GitHub Actions workflow to automate future releases.
PR #17 includes the following updates:
- Updates the unique test for
stg_mailchimp__members
to include bothmember_id
andlist_id
, as these make up the unique key for the respective source table.
- Updates the seed data used in integration testing to include a new record for an existing
member_id
with a newlist_id
.
- Databricks compatibility! (#15)
- Incorporated the new
fivetran_utils.drop_schemas_automation
macro into the end of each Buildkite integration test job. (#14) - Updated the pull request templates. (#14)
PR #12 includes the following breaking changes:
- Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically
{{ dbt_utils.<macro> }}
have been updated to{{ dbt.<macro> }}
for the below macros:any_value
bool_or
cast_bool_to_text
concat
date_trunc
dateadd
datediff
escape_single_quotes
except
hash
intersect
last_day
length
listagg
position
replace
right
safe_cast
split_part
string_literal
type_bigint
type_float
type_int
type_numeric
type_string
type_timestamp
array_append
array_concat
array_construct
- For
current_timestamp
andcurrent_timestamp_in_utc
macros, the dispatch AND the macro names have been updated to the below, respectively:dbt.current_timestamp_backcompat
dbt.current_timestamp_in_utc_backcompat
dbt_utils.surrogate_key
has also been updated todbt_utils.generate_surrogate_key
. Since the method for creating surrogate keys differ, we suggest all users do afull-refresh
for the most accurate data. For more information, please refer to dbt-utils release notes for this update.- Dependencies on
fivetran/fivetran_utils
have been upgraded, previously[">=0.3.0", "<0.4.0"]
now[">=0.4.0", "<0.5.0"]
.
- Updated README documentation for easier navigation and dbt package setup.
- Included the
mailchimp_[source_table_name]_identifier
variables for easier flexibility of the package models to refer to differently named sources tables.
🎉 dbt v1.0.0 Compatibility 🎉
- Adjusts the
require-dbt-version
to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.- For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
- For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
- Upgrades the package dependency to refer to the latest
dbt_fivetran_utils
. The latestdbt_fivetran_utils
package also has a dependency ondbt_utils
[">=0.8.0", "<0.9.0"].- Please note, if you are installing a version of
dbt_utils
in yourpackages.yml
that is not in the range above then you will encounter a package dependency error.
- Please note, if you are installing a version of
- Updating src_mailchimp database variable to reflect README files. Update
database
tomailchimp_database
.(#7).
- @dfagnan (#7).
- This is the initial release of this package. For more information refer to the README.