Define the Presto Connector Initiator Catalog Properties | QueryGrid - Defining the Initiator Catalog Properties File - Teradata QueryGrid

QueryGridâ„¢ Installation and User Guide - 3.06

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata QueryGrid
Release Number
3.06
Published
December 2024
ft:locale
en-US
ft:lastEdition
2024-12-07
dita:mapPath
ndp1726122159943.ditamap
dita:ditavalPath
ft:empty
dita:id
lxg1591800469257
Product Category
Analytical Ecosystem
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.

  1. Log on to the control node where Starburst Admin is installed.
  2. Change the directory to the Starburst Admin path.
  3. 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
  4. 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.yml
    The 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.
  5. Restart the Presto cluster.
    ansible-playbook -i playbooks/inventory_hdp123_hosts playbooks/restart.yml
  6. 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