Skip to main content

Presto Connections

Note

This feature may not be available in all product editions. For more information on available features, see Compare Editions.

Presto is a high-performance, distributed SQL engine for running interactive analytic queries against data sources of all sizes ranging from Gigabytes to Petabytes. The architecture of Presto enables users to query various data sources such as Hadoop, MYSQL, MongoDB, and Teradata. For more information, see https://prestodb.io/.

Tip

This connection is in early preview. It is read-only and available only in SaaS product editions. For more information on early previews, see Early Preview Connection Types.

Limitations and Requirements

Note

During normal selection or import of an entire table, you may encounter an error indicating a problem with a specific column. Since some tables require filtering based on a particular column, data from them can only be ingested using custom SQL statements. In this case, the problematic column can be used as a filter in the WHERE clause of a custom SQL statement to ingest the table.

  • For more information, please consult the CData driver documentation for the specific table.

  • For more information on using custom SQL, see Create Dataset with SQL.

Note

For filtering date columns, this connection type supports a set of literal functions on dates. You can use these to reduce the volume of data extracted from the database using a custom SQL query. For more information, see the pg_dateliteralfunctions.htm page in the driver documentation for this connection type.

  • Presto supports NoAuth and Basic (LDAP) authentication.

  • Presto has double PATH metadata, that is, Catalog and Schema. You can import tables only after the selection of Catalog and Schema.

    presto_dbdoctest/mysql/classicmodels

    Where, mysql is the catalog and classicmodels is the Schema.

  • While importing data through custom SQL, insert custom SQL statements as SELECT * from catalog.schema.tableName.

Create Connection

via Dataprep by Trifacta application

When you create the connection, please review the following properties and specify them accordingly:

Connection Property

Description

Host

The host name or IP address of the Presto REST server. Example:

54.190.171.138

Enable SSL

Select the checkbox to enable SSL connections to Presto.

Connect String Options

The following value sets the connection timeout:

UseSSL=true;SSLServerCert=*

For using with out SSL, a certification file is required, UseSSL=true;Timeout=0;SSLServerCert=/Users/skakita/presto_cert.cer. (if not trusted certificate is used).

If you enable SSL, use this: UseSSL=true;SSLServerCert=* The above is used to trust any kind of SSL certificate.

* Implies wild card, that is, ignore SSL certificate validation.

Port

The port for the Presto REST server. The default value is 8080.

Credential Type

The scheme used for authentication. The following are the available options:

  • NoAuth: If the Presto server runs without authentication.

  • Basic: If the Presto server runs in File or LDAP authentication mode.

Note

If you select Basic, then the User Name and Password fields are displayed.

User Name

Username to connect to Presto

Password

The password associated with the above user name.

Default Column Data Type Inference

Leave this value as Enabled.

For more information, see the driver documentation https://cdn.cdata.com/help/ORG/jdbc/default.htm.

via API

Depending on your product edition, you can create connections of this type. Key information:

"vendor": "presto_db",
"vendorName": "Presto DB",
"type": "jdbc"

For more information, see

Dataprep by Trifacta: API Reference docs

Data Type Conversions

For more information, see the driver documentation https://cdn.cdata.com/help/ORG/jdbc/default.htm.

In this section: