E-MapReduce (EMR) provides built-in Trino connectors that you can modify or extend with custom connectors.
Built-in Trino connectors in EMR
EMR Trino includes the following built-in connectors.
|
Connector |
Description |
References |
|
Hive |
The Hive connector lets you query data in a Hive data warehouse. |
|
|
Kudu |
The Kudu connector lets you query, insert, and delete data in Kudu. |
|
|
MySQL |
The MySQL connector lets you query and create tables in an external MySQL instance. |
|
|
Iceberg |
The Iceberg connector lets you query data files in Iceberg format. |
|
|
Hudi |
The Hudi connector lets you query Copy on Write (COW) and Merge on Read (MOR) tables. |
|
|
Delta |
The Delta connector lets you query Delta Lake tables. |
|
|
JMX |
The JMX connector enables system monitoring and debugging. |
|
|
system |
The system connector lets you query cluster information and metrics. Note
The system connector requires no configuration. All information is available through the |
None |
Modify a built-in connector
You can modify the configuration file for each connector on the Configure tab of the Trino service in the EMR console. The following table maps each connector to its configuration file.
|
Connector |
Configuration file |
|
Hive |
hive.properties |
|
Kudu |
kudu.properties |
|
MySQL |
mysql.properties |
|
Iceberg |
iceberg.properties |
|
Hudi |
hudi.properties |
|
Delta |
delta.properties |
|
JMX |
jmx.properties |
|
system |
system.properties |
Example: Modify the Hive connector
-
On the Configure tab for the Trino service in the EMR console, in the Service Configuration section, click the hive.properties tab.
-
Modify the configuration items as needed.
See Manage configuration items for details.
-
After saving the configuration, select in the upper-right corner.
NoteAfter the service restarts, the connector is ready to use.
Add a custom connector
This feature is available only in EMR V3.27.0, V4.3.0, V5.2.0, and later versions.
By default, EMR Trino provides five placeholder connectors for custom use: connector1 through connector5. These correspond to the connector1.properties, connector2.properties, connector3.properties, connector4.properties, and connector5.properties files on the Configure tab of the Trino service. The configuration process is the same as for built-in connectors.
To add a custom connector, modify the configuration of an unused placeholder connector.
Example: Add a MongoDB connector
-
On the Configure tab for the Trino service in the EMR console, in the Service Configuration section, click the connector1.properties tab.
-
Set connector.name to mongodb.
-
Add custom configuration items as needed.
See Modify configuration items for details.
-
After saving the configuration, select in the upper-right corner.
NoteAfter the service restarts, the connector is ready to use.