You define catalog properties for the Presto connector in a properties file that is manually created and edited. This is different than the Teradata connector properties, which are defined using the QueryGrid portlet.
The Presto catalog properties file references a data source and maintains the set of properties associated with that data source connector. You can have one or more catalogs per connector. The Presto connector can have multiple initiator catalogs, one for each link and version pair. The catalog properties file is analogous to the CREATE FOREIGN SERVER statement for the Teradata connector.
After manually editing the file, you must restart the Presto server for the new configuration to take effect.
- Log on to the control node where Starburst Admin is installed.
- Change the directory to the Starburst Admin path.
- Create and edit an initiator catalog properties file: files/catalog/name.properties. For example, create and edit a file named tdh234m1sdld0461_active.properties and add the following content to the file:
connector.name=qginitiator qginitiator.linkName=tdh234m1sdld0461 qginitiator.version=active
- Run playbooks/push-configs.yml to push the properties file on all nodes.For example:ansible-playbook -i playbooks/inventory_hdp123_hosts playbooks/push-configs.ymlThe playbook push-configs.yml command pushes all the configuration files, catalogs, and plugin directories present in the files directory to the nodes. So, make sure the previous cleanup is performed.
- Restart the Presto cluster.ansible-playbook -i playbooks/inventory_hdp123_hosts playbooks/restart.yml
- From Trino CLI, use the SHOW CATALOGS command to verify the newly created properties file exists.Run:
tdh234m1:~ # trino-cli --server localhost:8090 trino> show catalogs;Result:
Catalog ------------------------- hive system tdh234m1sdld0461_active tpch