If you're using the dbt CLI, you'll need to set up a
You can learn more about this in the article on Connecting to your warehouse.
This article lists the parts of your
profiles.yml which are not database specific. Check out the article for your database for exact connection details.
partial_parse: <true | false>use_colors: <true | false>printer_width: <integer>send_anonymous_usage_stats: <true | false><profile-name>:target: <target-name>outputs:<target-name>:type: <bigquery | postgres | redshift | snowflake | other>schema: <schema_identifier>threads: <natural_number>### database-specific connection details...<target-name>: # additional targets...<profile-name>: # additional profiles...
See the docs on partial parsing for details on functionality. By default,
partial_parse is set to
false. To enable partial parsing for all dbt projects you run locally, specify
partial_parse: true in your
You can also turn partial parsing on or off via command line flags. The CLI flags (
--no-partial-parse) will take precedence over the config set in
By default, dbt will colorize the output it prints in your terminal. You can turn this off by adding the following to your
By default, dbt will print out lines padded to 80 characters wide. You can change this setting by adding the following to your
We want to build the best version of dbt possible, and a crucial part of that is understanding how users work with dbt. To this end, we've added some simple event tracking to dbt (using Snowplow). We do not track credentials, model contents or model names (we consider these private, and frankly none of our business).
Usage statistics are fired when dbt is invoked and when models are run. These events contain basic platform information (OS + python version). You can see all the event definitions in
By default this is turned on – you can opt out of event tracking at any time by adding the following to your