SELECT | Presto Connector | QueryGrid - SELECT Syntax for the Presto Connector - 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
lifecycle
latest
Product Category
Analytical Ecosystem

You can use catalog_name.schema_name.table_name in the SELECT statements of your queries. If you do not specify a database, it defaults to the database that is configured for the connector properties in the QueryGrid portlet.

You can use this foreign server grammar in joins and any other place that you reference a normal table, including views, macros, and stored procedures.

Logical expressions such as AND, OR, GT, LT, LE, GE, EQ, ISNULL, IS NOT NULL, IN, and NOT IN are supported pushdown predicates.

For data type mappings from Teradata to Presto and Presto to Teradata, see Data Type Mapping for QueryGrid Connectors.

Example: Presto to Teradata SELECT

The example shows an import initiated on Presto to fetch data from a remote Teradata system. The query predicates to be pushed are provided to the connector in the Constraint class by the Presto server and used for pushdown to the remote Teradata system.

SELECT MAKE, MODEL FROM QG_TD1.DB1.TD_CARDATA WHERE MAKE = 'BUICK';
make    model
------  --------------------
Buick   Century
Buick   Enclave

Where QG_TD1 is the catalog used to reference the Presto-to-Teradata link. DB1 is the database or schema name on the remote system, and TD_CARDATA is the table on the remote system.