Trino Reverse ETL Source

Trino is a distributed SQL query engine for efficient, low-latency big data analytics.

RudderStack supports Trino as a data source from which you can ingest data and route it to your desired downstream destinations.

Prerequisites: Trino server setup

Before you set up Trino as a source in RudderStack, make sure your Trino server is configured correctly by following these sections:

• RudderStack supports only password file authentication mechanism for this source. Make sure to enable password file authentication for your Trino instance and create a password file.
• RudderStack uses the file-based access control mechanism for Trino. To use the access control plugin, see Configuration section.
• This integration supports only the Apache Hive connector currently. To use this connector, make sure to add the following configuration in the catalog properties file using the Hive connector:

hive.allow-drop-table=true
hive.metastore.thrift.delete-files-on-drop=true

Grant permissions

Before you set up Trino as a source, you must grant certain permissions on your Trino instance for RudderStack to access data from it.

Run the SQL queries listed in the following sections in the exact order to grant these permissions:

Step 1: Assign read access to tables

This step gives RudderStack the necessary permissions to read the relevant table records in Trino.

RudderStack uses the file-based access control mechanism for this integration.

To sync a table sample_table in user_schema for a user test, copy the below JSON in to your access control config JSON file:

{
  "tables": [{
    "user": "test",  // Replace with your RudderStack user name
    "catalog": "catalog_name ", // Replace with the catalog you wish to sync
    "schema": "user_schema ", 
    "table": "sample_table ",
    "privileges": ["SELECT"]
  }]
}

Step 2: Create RudderStack schema and grant permissions

CREATE SCHEMA "_rudderstack"

To add this schema to a particular location, run the following query:

CREATE SCHEMA "_rudderstack" WITH (location = "s3://<your_location>/")

Make sure to create the _rudderstack schema before syncing your data.

Step 3: Grant ownership to _rudderstack schema

The following grants RudderStack the necessary permissions to perform relevant actions on the tables in the _rudderstack schema:

{
  "catalogs": [{
    "user": "test",
    "catalog": "catalog_name ",
    "allow": "all"
  }],
  "schemas": [{
    "user": "test",
    "catalog": "catalog_name ",
    "schema": "_rudderstack ",
    "owner": true
  }],
  "tables": [{
    "user": "test",
    "catalog": "catalog_name ",
    "schema": "_rudderstack ",
    "privileges": ["SELECT",
      "INSERT",
      "DELETE",
      "UPDATE",
      "OWNERSHIP"
    ]
  }]
}

Set up Trino source in RudderStack

1. Log in to your RudderStack dashboard.
2. On the Connections page, click Add source.
3. Under Sources, click Reverse ETL and select Trino.

Configure warehouse credentials

You can choose to proceed with your existing warehouse credentials if you have configured them in the RudderStack dashboard previously. Otherwise, click Add new credentials to add new credentials for your warehouse.

• Host: Enter the host name or IP address of your Trino coordinator server.

Make sure to enter only the host name and not the complete URL. Otherwise, you will encounter an error.

For example, if the URL is https://trino-server.example.com, host name should be trino-server.example.com.

• Catalog Name: Specify the catalog to use when RudderStack executes queries in Trino.
• User: Enter the user with relevant access to the above settings.
• Password: Enter the password for the above user.
• Port: Enter the port number of your Trino coordinator server. This is an optional setting.

Click the Verify button on the top right. RudderStack will then verify and validate your credentials. Once verified, click Continue to proceed.

Specify name and source type

Specify the source name and type in this step.

• Source name: Assign a name to uniquely identify the source in the RudderStack dashboard.
• Select your source type: RudderStack lets you set up a Reverse ETL source from a warehouse Table, Model, or Audience.

Use warehouse table as source

Under Select your source type, choose Table and specify the below fields:

• Schema: Select the warehouse schema from the dropdown.
• Table: Choose the required table from which RudderStack syncs the data.
• Primary key: Select the column from the above table that uniquely identifies your records in the warehouse.

RudderStack uses the primary key column for diffing in case of incremental syncs. You can generate it by:

• Generating your table with a primary key, OR
• Creating a table view

You can use a composite key in cases where one column cannot be considered as a primary key. For example, you can a declare a composite key of user_id and timestamp by creating a view on your warehouse table.

Finally, review and complete your source setup.

Use model as source

Under Select your source type, choose Model and click Continue.

To configure a model as source:

1. Enter an optional description and specify the custom SQL query in Query section.
2. Click Run Query to fetch the data preview.
3. Select the Primary key to use a column that uniquely identifies your warehouse records.

You can set a primary key only after you run the SQL query successfully using the Run Query option.

RudderStack uses the primary key column for diffing in case of incremental syncs. You can generate it by:

• Generating your table with a primary key, OR
• Creating a table view

You can use a composite key in cases where one column cannot be considered as a primary key. For example, you can a declare a composite key of user_id and timestamp in SQL query of the model.

Finally, review and complete your source setup.

Use audience as source

Under Select your source type, choose Audience and follow these steps:

1. Configure your audience source by specifying the below fields:

   • Schema: Select the warehouse schema from the dropdown.
   • Table: Choose the required table from which RudderStack syncs the data.
   • Primary key: Select the column from the above table that uniquely identify your records in the warehouse.

RudderStack uses the primary key column for diffing in case of incremental syncs. You can generate it by:

• Generating your table with a primary key, OR
• Creating a table view

You can use a composite key in cases where one column cannot be considered as a primary key. For example, you can a declare a composite key of user_id and timestamp by creating a view on your warehouse table.

2. Set your audience conditions.
3. Click Preview to see the resulting data. Then, click Continue to proceed.

Finally, review and complete your source setup.

Review and complete setup

To make any changes to the warehouse credentials or source configuration, click the edit icon present next to those sections.

Review your configuration and click Create source to complete the setup.

Connect destination

You can connect this source to an existing or new destination to start using it. To connect to a destination later, click Done on the top right.

You will then be redirected to the Overview page of the source where you get the option of connecting it to an existing or new destination.

See Set up Reverse ETL Connection section for more information.

Update source configuration and settings

Go to the Configuration tab of your Reverse ETL source to update the configuration depending on your source type:

You cannot change the source type on this page.

The below table lists the options you can update:

After updating the configuration, the next sync will be a full sync.

Go to the Settings tab to:

• Get your source ID.
• Change your warehouse credentials.
• Set up custom alerts for your Reverse ETL source.
• Delete the source permanently.

You cannot delete a source that is connected to any destination.

FAQ

Which Trino connectors are supported for the Trino source integration?

The Trino source supports only the Apache Hive connector currently.

To use this connector, make sure to add the following configuration in your object store:

hive.allow-drop-table=true
hive.metastore.thrift.delete-files-on-drop=true

Which data types are supported for this integration?

The Trino source supports all data types listed in the Trino documentation except the Row data type.

What do the three validations under Verifying Credentials imply?

When setting up a Reverse ETL source, you will see the following three validations under the Verifying Credentials option once you proceed after entering the warehouse credentials:

These options are explained below:

• Verifying Connection: This option indicates that RudderStack is trying to connect to the warehouse with the provided warehouse credentials.

If this option gives an error, it means that one or more fields specified in the warehouse credentials are incorrect. Verify your credentials in this case.

• Able to List Schema: This option checks if RudderStack is able to fetch all schema details by using the provided credentials.
• Able to Access RudderStack Schema: This option implies that RudderStack is able to access the _rudderstack schema you have created by running all commands in the User Permissions section.

If this option gives an error, verify if you have successfully created the _rudderstack schema and given RudderStack the required permissions to access it.

What is the difference between the Table, Model, and Audience options when creating a Reverse ETL source?

When creating a new Reverse ETL source, you are presented with the following options from which RudderStack syncs the data:

Questions? Contact us by email or on Slack