Fix: Various Databricks related fixes#1036
Merged
Merged
Conversation
izeigerman
reviewed
Jun 26, 2023
izeigerman
reviewed
Jun 26, 2023
izeigerman
approved these changes
Jun 26, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Note: This PR has Databricks do a non-transactional delete + insert due to issues with dynamic insert/overwrite on Unity catalog tables. Once a
REPLACE WHEREbug is fixed we will be switching to that which will make it atomic again.The
USE CATALOGapproach from before only worked if SQL was being executed. So if you had a Dataframe then that catalog would not be used. ThesetCurrentCatalogworks across both SQL and Dataframe API.