Upgrade to dbt-athena v1.8.2 to fix cloning of Python models #479
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wrridgeway
approved these changes
May 29, 2024
jeancochrane
deleted the
jeancochrane/upgrade-dbt-athena-to-1.8.2-to-fix-cloning
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
dbt cloneworkflow we recommend in our README to our team members who are setting up dev environmens has been broken since #422 due to a bug in the way that the dbt-athena adapter handles cloning Python models (dbt-labs/dbt-athena#645). That bug was fixed in dbt-labs/dbt-athena#651 and has now been officially released in (v1.8.2)[https://github.com/dbt-athena/dbt-athena/releases/tag/v1.8.2], so this PR updates the dependency to fix the bug on our end as well.I tested this by running
dbt clone --select reporting.ratio_stats --state master-cachelocally to confirm that it completed successfully.