-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Unify the lookup for the various macros, all of them are done in the manifest now: - dbt's built-in package + all plugins are part of 'core' - finding macros has the concept of an optional package name - materializations are a special case of finding macros - the `generate_*_name` macros are another special case (non-core dependency packages are ignored) - generating the macro execution context now uses the concept of an optional search_package_name - macro execution now binds these two together Unify the lookup for models/docs/sources - added a search_name property to those three types - create a 'Searchable' protocol, have the node search code accept that - simplify matching logic/push it into the correct types accordingly Rename get_materialization_macro to find_materialization_macro_by_name (consistency) context namespacing behavior: - dbt run-operation now passes the named package along to macro execution if a package name is specified - so `dbt run-operation dependency.ad` runs with the dependency namespace as local, overriding globals - but `dbt run-operation my_macro` runs in the current package namespace as local, even if it ultimately runs the dependency's my_macro() - the current package namespace is always treated as "global", overriding core macros Tons of tests
- Loading branch information
Jacob Beck
committed
Jan 29, 2020
1 parent
e570d22
commit 62755fe
Showing
18 changed files
with
1,008 additions
and
229 deletions.
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.