-
Notifications
You must be signed in to change notification settings - Fork 40
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
[Bug Fix] Remove incremental logic #97
Changes from 7 commits
17a46d3
7610760
318fc27
56f243d
a96514b
d8b48ad
8904f43
0838104
57101e2
a2b83e0
3fa1b1c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The package version for this package is still referencing the old v0.15.0 for dbt_shopify. This needs to be updated to reflect the latest version range. |
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,4 @@ | ||
packages: | ||
- package: fivetran/shopify_source | ||
version: [">=0.14.0", "<0.15.0"] | ||
- git: https://github.com/fivetran/dbt_shopify_source.git | ||
revision: bugfix/redshift-limit-one | ||
warn-unpinned: false | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Reminder to swap before release
fivetran-avinash marked this conversation as resolved.
Show resolved
Hide resolved
|
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.
My understanding was that it was the incremental strategy in general and not limited to
merge
, especially since we had the models in question materializing as tables by default for BQ and Databricks, and delete+insert uses the same unique-key logic. Is this not the case? Unless I am mistaken, I would recommend generalizing it a bit: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 wasn't certain, as the majority of the conversation centered around
merge
. I've tweaked this a little, let me know if this looks good!