-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Configure which schemas models are materialized in #284
Comments
+1! |
This would be great to have in addition to default target as right now in I imagine this to be something like a configuration value for model. {{
config(
materialized = 'table',
schema = 'dbt'
)
}}```
`schema` keyword is also used for `schema.yml` but should be clear enough from context what is being referenced. |
Would it be possible to pass the schema as either a string or a dictionary that was keyed on target name (ie, dev/prod) this would potentially allow for schema targets to be configured without breaking multiple environments? |
This directly approaches my use case @ https://getdbt.slack.com/archives/C0VLZM3U2/p1497459181879656 |
Happy to report that this has been merged into We'll be publishing our second 0.9.0 alpha release (including this feature) in the next day or two -- please let me know if you're interesting in trying it out! Relevant docs: https://dbt.readme.io/v0.9/docs/using-custom-schemas |
Schema Test - Not accepted values, test fixed empty lines at the end Update changelog
Semi-related: #198
This would be useful for both organization and permission configuration
The text was updated successfully, but these errors were encountered: