Skip to content

Latest commit

 

History

History
22 lines (16 loc) · 2.5 KB

DECISIONLOG.md

File metadata and controls

22 lines (16 loc) · 2.5 KB

Decision Log

Usage Cost vs Credits Used Sources

This package takes into consideration that the Fivetran pricing model has adjusted over the years. In particular, this package considers the old credit model (captured within the credits_used source) and the newer usage model (captured within the usage_cost source). By default, this package will dynamically check the mentioned sources in your destination and generate the respective staging models if the source is found. If the source is not found, the package will create a single row of null records in order to imitate the schema structure and ensure downstream transformations succeed. See the does_table_exist() macro for more information on this dynamic functionality.

The below variables control the respective behaviors and may be overridden if desired. If overridden and configured to false, the models will still be materialized, but it will return no rows. This ensures the package does not generate records from the source, but still materializes the schema to ensure there is no run failure. The intention is that these variables are not needed to be configured, but if necessary they are available.

vars:
  fivetran_platform__usage_pricing: true ## Dynamically checks the source at runtime to set as either true or false. May be overridden using this variable if desired.
  fivetran_platform__credits_pricing: false ## Dynamically checks the source at runtime to set as either true or false. May be overridden using this variable if desired.

Transformation Runs

Not all customers have the transformation_runs source table, particularly if they are not using Fivetran Transformations. Therefore, we leverage a new variable fivetran_platform_using_transformations, which automatically checks for the table. If it exists, the variable is set to True, which then persists the transformation_runs source table and related models and downstream fields. If the table doesn't exist, the staging stg_fivetran_platform__transformation_runs model will persist as an empty model and respective downstream fields will be null.

In the case you have the transformation_runs source table but still wish to disable it to prevent it from being populated in the package, you may set fivetran_platform_using_transformations to False in your project.yml:

vars:
  fivetran_platform_using_transformations: false ## Dynamically checks the source at runtime to set as either true or false. May be overridden using this variable if desired.