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

Fix insert_overwrite replacement edge case #697

Merged
merged 2 commits into from
Jun 7, 2024

Conversation

benc-db
Copy link
Collaborator

@benc-db benc-db commented Jun 6, 2024

Resolves #696

Description

The setting that enables insert_overwrite to selectively overwrite partitions also causes it to leave behind partitions when used with create or replace. Hence, ensure the setting is static on 'full-refresh', and dynamic on subsequent runs.

Checklist

  • 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
  • I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.

@benc-db benc-db merged commit f84a420 into main Jun 7, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Changing a non-incremental to incremental model leaves old data in the table
1 participant