From 0b9f33e32f808e44db2d7055c901591ef5dac3cc Mon Sep 17 00:00:00 2001 From: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Date: Tue, 7 Jan 2025 17:07:52 -0600 Subject: [PATCH 1/2] MagicBot/add-model-counts updates --- CHANGELOG.md | 6 ++++++ README.md | 10 ++++++---- 2 files changed, 12 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index aa9771d..7dff3ca 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,9 @@ +# dbt_stripe version.version + +## Documentation +- Added Quickstart model counts to README. ([#103](https://github.com/fivetran/dbt_stripe/pull/103)) +- Corrected references to connectors and connections in the README. ([#103](https://github.com/fivetran/dbt_stripe/pull/103)) + # dbt_stripe v0.15.1 ## Bug Fixes diff --git a/README.md b/README.md index dd2f51b..aaad81d 100644 --- a/README.md +++ b/README.md @@ -48,6 +48,8 @@ Curious what these tables can do? Check out example visualizations from the [str

+### Materialized Models +Each Quickstart transformation job run materializes 57 models if all components of this data model are enabled. This count includes all staging, intermediate, and final models materialized as `view`, `table`, or `incremental`. ## How do I use the dbt package? @@ -55,7 +57,7 @@ Curious what these tables can do? Check out example visualizations from the [str ### Step 1: Prerequisites To use this dbt package, you must have the following: -- At least one Fivetran Stripe connector syncing data into your destination. +- At least one Fivetran Stripe connection syncing data into your destination. - A **BigQuery**, **Snowflake**, **Redshift**, **Databricks**, or **PostgreSQL** destination. #### Databricks Dispatch Configuration @@ -109,8 +111,8 @@ vars: stripe__standardized_billing_model_enabled: true # false by default. ``` -#### Unioning Multiple Stripe Connectors -If you have multiple Stripe connectors you would like to use this package on simultaneously, we have added the ability to do so. Data from disparate connectors will be unioned together and be passed downstream to the end models. The `source_relation` column will specify where each record comes from. To use this functionality, you will need to either set the `stripe_union_schemas` or `stripe_union_databases` variables. Please also make sure the single-source `stripe_database` and `stripe_schema` variables are removed. +#### Unioning Multiple Stripe Connections +If you have multiple Stripe connections you would like to use this package on simultaneously, we have added the ability to do so. Data from disparate connections will be unioned together and be passed downstream to the end models. The `source_relation` column will specify where each record comes from. To use this functionality, you will need to either set the `stripe_union_schemas` or `stripe_union_databases` variables. Please also make sure the single-source `stripe_database` and `stripe_schema` variables are removed. ```yml # dbt_project.yml @@ -137,7 +139,7 @@ vars: ``` #### Leveraging Subscription Vs Subscription History Sources -For Stripe connectors set up after February 09, 2022 the `subscription` table has been replaced with the new `subscription_history` table. By default this package will look for your subscription data within the `subscription_history` source table. However, if you have an older connector then you must configure the `stripe__using_subscription_history` to `false` in order to have the package use the `subscription` source rather than the `subscription_history` table. +For Stripe connections set up after February 09, 2022 the `subscription` table has been replaced with the new `subscription_history` table. By default this package will look for your subscription data within the `subscription_history` source table. However, if you have an older connector then you must configure the `stripe__using_subscription_history` to `false` in order to have the package use the `subscription` source rather than the `subscription_history` table. > **Please note that if you have `stripe__using_subscription_history` enabled then the package will filter for only active records.** ```yml vars: From 8ef682ab1b9230f727c5f8361b166e8a09bfc3e6 Mon Sep 17 00:00:00 2001 From: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com> Date: Thu, 9 Jan 2025 14:17:20 -0800 Subject: [PATCH 2/2] more connector->connection changes --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index aaad81d..b645dbd 100644 --- a/README.md +++ b/README.md @@ -139,11 +139,11 @@ vars: ``` #### Leveraging Subscription Vs Subscription History Sources -For Stripe connections set up after February 09, 2022 the `subscription` table has been replaced with the new `subscription_history` table. By default this package will look for your subscription data within the `subscription_history` source table. However, if you have an older connector then you must configure the `stripe__using_subscription_history` to `false` in order to have the package use the `subscription` source rather than the `subscription_history` table. +For Stripe connections set up after February 09, 2022 the `subscription` table has been replaced with the new `subscription_history` table. By default this package will look for your subscription data within the `subscription_history` source table. However, if you have an older connection, then you must configure the `stripe__using_subscription_history` to `false` in order to have the package use the `subscription` source rather than the `subscription_history` table. > **Please note that if you have `stripe__using_subscription_history` enabled then the package will filter for only active records.** ```yml vars: - stripe__using_subscription_history: False # True by default. Set to False if your connector syncs the `subscription` table instead. + stripe__using_subscription_history: False # True by default. Set to False if your connection syncs the `subscription` table instead. ``` #### Setting your timezone