dbt_fivetran_log v0.6.0

Happy Monday!

This release of the dbt_fivetran_log package includes the following updates:

🚨 Breaking Changes 🚨

• This release includes updates to the fivetran_log__credit_mar_destination_history and stg_fivetran_log__credits_used models to account for the new Fivetran pricing model. These changes include: (#50)
  • stg_fivetran_log__credits_used
    • The field credits_consumed has been renamed to credits_spent
  • fivetran_log__credit_mar_destination_history
    • The model has been renamed to fivetran_log__usage_mar_destination_history
    • The field credits_per_million_mar has been renamed to credits_spent_per_million_mar
    • The field mar_per_credit has been renamed to mar_per_credit_spent

🎉 Features 🎉

• README documentation updates for easier experience leveraging the dbt package. (#53)
• Added fivetran_log_[source_table_name]_identifier variables to allow for easier flexibility of the package to refer to source tables with different names. (#53)
• This package now accounts for the new Fivetran pricing model. In particular, the new model accounts for the amount of dollars spend vs credits spent. Therefore, a new staging model stg_fivetran_log__usage_cost has been added. (#50)
  • This model relies on the usage_cost source table. If you do not have this source table it means you are not on the new pricing model yet. Please note, the dbt package will still generate this staging model. However, the model will be comprised of all null records.
• In addition to the new staging model, two new fields have been added to the fivetran_log__usage_mar_destination_history model. These fields mirror the credits spent fields, but account for the amount of dollars spent instead of credits. (#50)
  • amount_spent_per_million_mar
  • mar_per_amount_spent

Under the Hood

• Introduces a new macro does_table_exist to be leveraged in the new pricing model updates. This macro will check the sources defined and provide either true or false if the table does or does not exist in the schema. (#50)