-
Notifications
You must be signed in to change notification settings - Fork 35
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
Feature/q3 2023 updates #69
Conversation
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-reneeli thanks for working through these changes. It seems that the most significant updates have been made to the balance transactions model which I can see being valuable to all users, not just the ones who will take advantage of these new reports!
I do have a number of requests for you to review and make appropriate updates.
Some major ones include my thoughts of renaming the fields in the staging models as opposed to the end model for consistency and allowing the focus of the transform models to be used for transformation purposes and not renaming. This also follows our intention of the source package. Following discussion with @fivetran-reneeli we will instead do the alias renaming in the final select statement. Updating the source will cause major scope creep although that is the preferred. Possibly we can open FR to make this update in the future.
Additionally, I wonder if we can consolidate the payout enhanced model with the balance transaction since they are almost identical. I would like to discuss those two in more detail before you move forward with updates.
See my other comments below and let me know if you have any questions. Thanks!
Co-authored-by: Joe Markiewicz <[email protected]>
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-reneeli thanks for making these updates and the new models are looking really good! I just have a few final comments (see the previous comments for any unresolved ones that should be addressed as well).
Once these updates are applied, be sure to address the source package review notes and then regen the docs. This should then be good to roll out!
Lastly you may need to use a new schema for integration tests as it looks like the Snowflake schema has conflicting role permissions now and is resulting in failed buildkite jobs.
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.
Thanks so much for working on these updates @fivetran-reneeli. This looks good to go to release review!
packages.yml
Outdated
# version: [">=0.9.0", "<0.10.0"] | ||
|
||
- git: https://github.com/fivetran/dbt_stripe_source.git | ||
revision: feature/q3-2023-updates | ||
warn-unpinned: false |
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.
Bumping this reminder before merge
Co-authored-by: Joe Markiewicz <[email protected]>
Co-authored-by: Joe Markiewicz <[email protected]>
PR Overview
This PR will address the following Issue/Feature: n/a
This PR will result in the following new package version: v 11
Significant updates to our Stripe package for Q3 2023.
Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
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 acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":
Confirm that these additions appear in the target schema when run
Standard Updates
Please acknowledge that your PR contains the following standard updates:
dbt Docs
Please acknowledge that after the above were all completed the below were applied to your branch:
If you had to summarize this PR in an emoji, which would it be?
💃