Refactoring the Adapter to prepare for metadata behavior flag #894
+597
−478
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
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.
Description
We've been having many performance issues with information_schema recently. This PR refactors the current behavior to a behavior module so that I can select between existing behavior and new behavior with a flag. Since this is a sizeable refactor, there are no behavior changes in this PR. The goal is just to exactly replicate the current behavior, but behind a new class so that I can select new behavior based on flag in the next PR. All tests have been minimally updated to pass; they are not good tests, but this behavior will eventually be replaced by the new behavior(s), so I don't feel like rewriting these old tests.
Checklist
CHANGELOG.mdand added information about my change to the "dbt-databricks next" section.