v0.8.0 dbt_greenhouse_source

PR #31 includes the following updates:

Breaking Changes

• Updated *_id fields in all staging models to be cast as strings to ensure compatibility in downstream joins by avoiding potential type mismatches.
  • Note: most IDs were previously stored as integers.

Documentation

• Updated README formatting.

Under the Hood

• Added an additional integration test to verify functionality when greenhouse_using_* variables are disabled.

Full Changelog: v0.7.0...v0.8.0

v0.7.0 dbt_greenhouse_source

PR #29 includes the following updates:

Bug Fixes

• Updated the logic for stg_greenhouse__tag and stg_greenhouse__user to account for the presence of the singularly or plurally-named titular source tables, tag(s) and user(s). In the case where there exists both versions of the table name, the package will use the plurally-named table.
  • The source table tag was renamed to tags for connectors created on or after July 18, 2024 and the table user was renamed to users in October 2024.
• This is a breaking change for customers with the plurally-named tables, as they have not been able to run the models previously.

Under the Hood

• Added the does_table_exist macro to check for differently named versions of the same source table.
• Removed custom fields from seed data and docs.
• Update the enable config in the src.yml so that freshness tests are not run for non-existent source tables.

Full Changelog: v0.6.0...v0.7.0

v0.6.0 dbt_greenhouse_source

This release of dbt_greenhouse_source incorporates the following changes:

🎉 Feature Update 🎉

• Databricks and PostgreSQL compatibility! (#25)

🚘 Under the Hood 🚘

• Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job. (#23)
• Updated the pull request templates. (#23)

dbt_greenhouse_source v0.5.0

PR #20 includes the following breaking changes:

🚨 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 and current_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
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

🎉 Documentation and Feature Updates 🎉:

• Updated README documentation for easier navigation and dbt package setup.
• Included the greenhouse_[source_table_name]_identifier variables for easier flexibility of the package models to refer to differently named sources tables.

dbt_greenhouse_source 0.4.1

Happy Monday!

This release of the dbt_greenhouse_source package includes the following updates:

Under the Hood

• Leveraged the {{ dbt_utils.type_timestamp() }} macro within the staging models for all timestamp fields.
  • This is needed as certain Redshift warehouses sync these fields as timestamptz by default which causes compilation errors in downstream models. This macro safely removes timezone values from the UTC timestamps and ensures success in downstream transformations.

dbt_greenhouse_source 0.4.0

🎉 dbt v1.0.0 Compatibility 🎉

🚨 Breaking Changes 🚨

• 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 latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
  • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.

dbt_greenhouse_source 0.3.1

Happy Tuesday!

Below are the following updates to the dbt_greenhouse_source package. For more details, refer to the CHANGELOG.

Bug Fixes

• Addition of the meta config within the relevant src_greenhouse.yml tables that are able to be disabled by the user. These configs allow the source freshness tests to skip over the disabled models. (#15)

dbt 0.20.0 Compatibility

🎉 dbt 0.20.0 Compatibility 🎉

🚨 This is a breaking change! 🚨 dbt v0.20.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package.

Additional considerations when upgrading to this package:

• This package utilizes the latest v0.7.x release of the dbt-labls/dbt_utils package. If your project also utilizes a version of the fishtown-analytics/dbt_utils package then you will receive a duplicate package error. If this is the case you will need to consider upgrading your other packages to be compatible with this update or use a previous release of this package.
• Similar to the above point, all previous Fivetran dbt packages utilize the fishtown-analytics/dbt_utils package and you will need to upgrade all Fivetran dbt packages to the latest dbt 0.20.0 compatibility releases in order for your packages to run without package conflicts.

Fivetran Utils Dependency Update

🚧 Fivetran Utils Dependency Update 🚧

This release includes the following non-breaking changes:

• Update to the packages.yml to reference the recently released Fivetran Utils package. This is a necessary update to ensure this package is compatible with previous dbt releases before dbt v0.20.0 updates take place.

Package Upgrades

This new release does two main things:

1. Incorporates variables to disable staging models related to the Greenhouse OFFICE, JOB_OFFICE, DEPARTMENT, and JOB_DEPARTMENT tables.
2. Breaking change (somewhat): Incorporates custom schemas to better organize package models. By default, staging models will be written to <target_schema> + _stg_greenhouse.