Skip to content
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

[ADAP-631] Convert Target_lag to str type to add Downstream option #732

Merged
merged 35 commits into from
Aug 14, 2023

Conversation

McKnight-42
Copy link
Contributor

@McKnight-42 McKnight-42 commented Aug 9, 2023

resolves #
docs dbt-labs/docs.getdbt.com/#

Problem

We need to allow for all target lags variations that Snowflake accepts. Variations include:

Solution

change expected type to str

TODO:

  • merge ADAP-774
  • update functional tests to check for downstream option.
  • work on validation options (if possible)
  • create changelog

Checklist

  • I have read the contributing guide and understand what's expected of me
  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

@McKnight-42 McKnight-42 added the Skip Changelog Skips GHA to check for changelog file label Aug 9, 2023
@McKnight-42 McKnight-42 requested a review from a team as a code owner August 9, 2023 16:17
@McKnight-42 McKnight-42 removed the Skip Changelog Skips GHA to check for changelog file label Aug 10, 2023
Copy link
Contributor

@mikealfare mikealfare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add a test that verifies that we can pass "downstream" into target_lag and successfully create a dynamic table.

@mikealfare mikealfare dismissed their stale review August 11, 2023 21:31

I forgot to point out the test case.

@McKnight-42
Copy link
Contributor Author

Let's add a test that verifies that we can pass "downstream" into target_lag and successfully create a dynamic table.

Added a test following the current method of alter and seeing if a run is successful till we find a way to check the show command stuff via test suite. also would want to flag that might be good to be able to pass new param into methods like change_config_via_alter in end version so we don't have to duplicate it for every version we want.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this got caught in here accidentally.

Copy link
Contributor Author

@McKnight-42 McKnight-42 Aug 14, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah forgot one for the #727 so added it here instead of trying to do a entire revert, and add since we don't tie the pr to the changelog anymore and this pr was reliant on that pr to pass
.

Copy link
Contributor

@mikealfare mikealfare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good; I would just check that extra changie log.

@McKnight-42 McKnight-42 merged commit 73ea41a into main Aug 14, 2023
13 checks passed
@McKnight-42 McKnight-42 deleted the mcknight/ADAP-631 branch August 14, 2023 18:19
@github-actions
Copy link
Contributor

The backport to 1.6.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-732-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 73ea41ae5d29add8b448c1b9c5fdb84b4a580450
# Push it to GitHub
git push --set-upstream origin backport-732-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest

Then, create a pull request where the base branch is 1.6.latest and the compare/head branch is backport-732-to-1.6.latest.

@github-actions
Copy link
Contributor

The backport to 1.6.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-732-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 73ea41ae5d29add8b448c1b9c5fdb84b4a580450
# Push it to GitHub
git push --set-upstream origin backport-732-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest

Then, create a pull request where the base branch is 1.6.latest and the compare/head branch is backport-732-to-1.6.latest.

@github-actions
Copy link
Contributor

The backport to 1.6.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-732-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 73ea41ae5d29add8b448c1b9c5fdb84b4a580450
# Push it to GitHub
git push --set-upstream origin backport-732-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest

Then, create a pull request where the base branch is 1.6.latest and the compare/head branch is backport-732-to-1.6.latest.

@github-actions
Copy link
Contributor

The backport to 1.6.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-732-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 73ea41ae5d29add8b448c1b9c5fdb84b4a580450
# Push it to GitHub
git push --set-upstream origin backport-732-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest

Then, create a pull request where the base branch is 1.6.latest and the compare/head branch is backport-732-to-1.6.latest.

philippe-boyd-maxa pushed a commit to maxa-ai/dbt-snowflake that referenced this pull request Nov 27, 2023
…bt-labs#732)

* update RELEASE_BRANCH env

* initial push for ADAP-631 to convert target_lag to a str type

* readd SnowflakeDynamicTableTargetLagConfigChange class as part of dynamic_table.py

* pull in ADAP-774 and add changelog

* add missing changelog entry for pr 727

* update to main, and add basic test case for passing downstream via alter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants