Configuration (setting up your profile)
To connect dbt Core to your Presto engine, configure the profiles.yml file that is located in .dbt of your home directory.
Note: You can either copy or export the Presto connection details to create the
profiles.yml. To do that, see Getting connection information.
watsonx.data on Red Hat® OpenShift®
watsonx.data Developer edition
The following is an example configuration:
my_project:
outputs:
on-prem:
type: watsonx_presto
method: BasicAuth
user: username
password: password
host: internal/external host
port: 443
catalog: analytics
schema: dbt_drew
threads: 8
ssl_verify: path/to/certificate
target: on-prem
The following table covers the parameter details:
| Option | Required/Optional | Description | Example |
|---|---|---|---|
type |
Required | Specifies the type of connection to be used. Set the connection type to
watsonx_presto to indicate that you are using the dbt watsonx Presto adapter for
watsonx.data Presto. |
watsonx_presto |
method |
Required (default method is BasicAuth) |
Authentication method for Presto. |
BasicAuth |
user |
Required | Username for authentication. | drew |
password |
Required if method is BasicAuth |
Password or API key for authentication. | None or alphanumeric |
http_headers |
Optional | HTTP headers to send alongside requests to Presto, specified as a yaml dictionary of (header, value) pairs. | X-Presto-Routing-Group: my-cluster |
http_scheme |
Optional (default is http or https for method:
BasicAuth) |
HTTP scheme to use (http or https). |
https or http |
catalog |
Required | Catalog name for building models. | Analytics |
schema |
Required | Schema for building models. | dbt_drew |
host |
Required | Hostname for connecting to Presto. You can get the hostname by clicking View connect details in the engine details page. | 127.0.0.1 |
port |
Required | Port for connecting to Presto. You can get the port by clicking View connect details in the engine details page. | 8080 |
threads |
Optional (default is 1) | Number of threads for dbt operations. | 8 |
ssl_verify |
Optional | Path to the SSL certificate. The SSL certificate path is required if you are not using a
secured connection. To obtain the certificate, run the following command and save the certificate
to the specified
location.
If you
already use a secured connection, you can skip this configuration. |
path/to/certificate |