Feature/external source config #1784
Merged
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
beckjake
reviewed
Sep 27, 2019
…/dbt into feature/external-source-config
|
@beckjake I think I got the testing situation sorted! |
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.
Adds external source table config. Related to #1318
Big idea: projects can assert metadata about an external table in the
sourcesYML, including file location, column types, and partitions. They can then call macros that consume the metadata and perform DDL operations.Initial spec, macros, and more details in the
dbt-external-tablespackageTODO:
schemacannot be set based ontarget. Users may reasonably expect the ability to alter and test external table definitions in development schemas without interfering with the production external table.