Preset
You can use Preset, a cloud service for Superset, to query and visualize data.
Supported Authentication Methods
- Use the username and password of an account in your Dremio cluster.
- Use the username of an account in your Dremio cluster and a personal access token (PAT) created in Dremio. To create a PAT, follow the steps in Creating a PAT. After you obtain a PAT, it is recommended that you URL-encode it. To encode it locally on your system, you can follow these steps:
- In a browser window, right-click an empty area of the page and select Inspect or Inspect Element, depending on your browser.
- In the top bar of the inspection pane, click Console.
- Type
encodeURIComponent("<PAT>")
, where<PAT>
is the personal access token. The URL-encoded PAT appears in red on the next line. You can highlight it and copy it to your clipboard.
Creating a Connection
- Click Settings in the top-right corner, and select Database Connections under Data.
- Click the +Database button in the top-right corner.
- Select Other from the Supported Databases field of the Connect a Database dialog.
- In the Display Name field, specify any name you prefer.
- In the Connect a Database dialog, follow these steps:
-
Select Other from the Supported Databases field.
-
In the Display Name field, name the new connection.
-
If you want to authenticate by using a username and password, specify in the SQLAlchemy URI field a URI that is in this format:
Format of URIs with username and password authenticationdremio://<username>:<password>@<host>:<port>[/option=value[;...]]
<username>
: The username of the Dremio account to use.<password>
: The password of the Dremio account to use.<host>
: The hostname or IP address of the coordinator node of the Dremio cluster.<port>
: The port to connect to on the coordinator node. Unless explicitly changed on the node, the port is 31010.[/option=value[;...]]
: One or more optional properties, separated by semicolons. See SSL Connection Properties and Advanced Properties.
dremio://myUserID:myPassword@myHost:31010/ssl=true;schema=Samples;routing_tag=thisTag
-
If you want to authenticate by using a personal access token, specify in the SQLAlchemy URI field a URI that is in this format:
Format of URIs with PAT authenticationdremio://<username>:<PAT>@<host>:<port>[/option=value[;...]]
<username>
: The username of the Dremio account to use.<PAT>
: The personal access token to use.<host>
: The hostname or IP address of the coordinator node of the Dremio cluster.<port>
: The port to connect to on the coordinator node. Unless explicitly changed on the node, the port is 31010.[/option=value[;...]]
: One or more optional properties, separated by semicolons. See SSL Connection Properties and Advanced Properties.
dremio://myUserID:myPAT@myHost:31010/ssl=true;schema=Samples;routing_tag=thisTag
-
Test the connection. If the test fails, check the syntax and values in the connection URI.
-
Click Connect.
-
SSL Connection Properties
Use the following properties to configure SSL encryption and verification methods:
Name | Type | Description | Default Value |
---|---|---|---|
UseEncryption | integer | Forces the client to use an SSL-encrypted connection to communicate with Dremio. Accepted values: true , the client communicates with Dremio by using SSL encryption; false , the client does not communicate with Dremio by using SSL encryption. | true |
disableCertificateVerification | integer | Specifies whether to verify the host certificate against the trust store. Accepted values: false , verifies the certificate against the trust store; true , does not verify the certificate against the trust store. | false |
trustedCerts | string | The full path of the .pem file containing certificates trusted by a CA, for the purpose of verifying the server. If this option is not set, defaults to using the trusted CA certificates .pem file.The TLS connection fails if you do not specify a value when UseEncryption is true and disableCertificateVerification is false. | N/A |
Advanced Properties
Name | Type | Description | Default Value |
---|---|---|---|
routing_queue | string | Specifies the queue to route queries to during a session. Direct Routing is used to specify the exact queue and execution cluster to run queries on for a given session. With Direct Routing, workload-management (WLM) rules are not considered; instead, queries are routed directly to the specified queue. For more information, see Workload Management. | N/A |
routing_tag | string | When this property is set, the specified tag is associated with all queries executed within a session. Rules can check for the presence of a tag with the function "tag()". For more information, see Workload Management. | N/A |