-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Releases/v0.12.latest #82
Conversation
Update code to include new 'delayed' status from Shopify
Update shopify__daily_shop model to include new 'delayed' status from Shopify
packages.yml
Outdated
version: [">=0.12.0", "<0.13.0"] | ||
# - package: fivetran/shopify_source | ||
# version: [">=0.12.0", "<0.13.0"] | ||
- git: https://github.com/fivetran/dbt_shopify_source.git |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will update prior to merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fivetran-jamie this PR looks good to me! There are a few minor comments and questions, but nothin that would block this from being approved. Please address these comments before initiating the release review, but this is good from my end otherwise!
count(distinct case when status = 'delivered' then fulfillment_id end) as count_fulfillment_delivered | ||
|
||
from source | ||
where happened_at > '2023-01-01' and happened_at < '2024-01-01' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reason for this filter? My only concern with this filter is if you run the integrity validation on a data set that doesn't have data for this period then it won't validate the results effectively. Is there a concern for removing this filter and running the validation for all records?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment for the other integrity tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah this was just me avoiding live-data messing things up, will adjust to be wider
count(count_customers) as count_customers, | ||
sum(order_adjusted_total) as order_adjusted_total, | ||
sum(count_abandoned_checkouts) as count_abandoned_checkouts, | ||
sum(count_fulfillment_attempted_delivery) as count_fulfillment_attempted_delivery, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This validation must have the shopify_using_fulfillment_event
variable defined as true
(default: false
) in order for the validation to succeed.
Would you either be able to put a conditional in here to ensure the validation runs as expected regardless of the variable being true/false. Or leave a comment to callout that the shopify_using_fulfillment_event
variable must be true
in order for this to succeed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah i'll add a conditional
order_metrics.count_orders as order_count_orders, | ||
daily_shop_metrics.order_adjusted_total as daily_shop_order_adjusted_total, | ||
order_metrics.order_adjusted_total as order_order_adjusted_total |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should add a coalesce here because if there are no orders at the source then the above ctes will produce null
records here. To ensure the where clause at the bottom is always accurate it would be best to treat a null
record as a 0
.
order_metrics.count_orders as order_count_orders, | |
daily_shop_metrics.order_adjusted_total as daily_shop_order_adjusted_total, | |
order_metrics.order_adjusted_total as order_order_adjusted_total | |
coalesce(order_metrics.count_orders, 0) as order_count_orders, | |
daily_shop_metrics.order_adjusted_total as daily_shop_order_adjusted_total, | |
coalesce(order_metrics.order_adjusted_total, 0) as order_order_adjusted_total |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added myself
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am assuming we named this "zontal_*" because the naming was too long for the warehouses. If so, I am okay with this approach but can we update our Slab documentation on validation tests to highlight this naming convention and be sure to share the standard with the team.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol no i can update -- i was just using slang for "horizontal" for funzies
CHANGELOG.md
Outdated
@@ -1,3 +1,13 @@ | |||
# dbt_shopify v0.12.1 | |||
|
|||
[PR #81](https://github.com/fivetran/dbt_shopify/pull/81) includes the following updates: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed this line and added the PRs to the exact change line items
|
||
## 🪲 Bug Fixes 🪛 | ||
- Added support for a new `delayed` fulfillment event status from Shopify. This produces a new `count_fulfillment_delayed` field in the `shopify__daily_shop` model. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd add your consistency/integrity tests as Under the Hood and that can be the #82 changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added!
This reverts commit 9dc9de3.
PR Overview
This PR will address the following Issue/Feature:
See upstream source PR for additional issue addressed
This PR will result in the following new package version:
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
🪲 Bug Fixes 🪛
delayed
fulfillment event status from Shopify. This produces a newcount_fulfillment_delayed
field in theshopify__daily_shop
model.Contributors
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps:
See Validation tests added
If you had to summarize this PR in an emoji, which would it be?
⏳