Limitations | Presto | QueryGrid - Known Limitations (Presto-to-Teradata) - 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
The following known limitations affect the use of Presto-to-Teradata links.
  • Transaction semantics between systems is not supported.
  • Import of temporal tables is not supported.
  • QueryGrid does not collect query metrics (such as CPU usage) for remote Teradata queries.
  • The maximum size supported for BLOB and CLOB is less than 2GB (2,097,088,000).
  • The maximum size of VARCHAR is 64k.
  • The temporary database name, NVP, is not supported on Teradata Database version 15.10.
  • The Foreign Function Execution (FFE) feature is not supported for the Presto target connector.
  • Use of Presto is limited to queries that can be performed in memory, so some queries may not be able to run in Presto that run in Hive.
  • After data has been exported and committed to a remote system, any subsequent errors or aborts on the local system do not roll back the remote request.

  • Presto does not support roles and access control unless Sentry is enabled.
  • QueryGrid does not support TimeWithTimeZone and TimestampWithTimeZone data types with Presto connectors.
  • When using the Explain command with a Presto initiator connector, remote query and execution plan data is not returned.
  • The default for Timestamp precision is three (3); QueryGrid truncates data with more than three decimal places. When a parameterized timestamp is used, QueryGrid truncates data with more than the precision of decimal places.
  • When using Predicate pushdowns, Array, Time, TimeWithTimeZone, Timestamp, and TimestampWithTimeZone data types are not pushed down.
  • Date literals used in WHERE clauses are not converted to the time zone of the remote system if the remote system time zone is different from the initiator system time zone.
  • UTF-16 supplementary characters longer than 2 bytes in a table cause data truncation.
  • Condition pushdown of the LIMIT clause is not supported.
  • Date literals used in WHERE clauses are not converted to the time zone of the remote system if the remote system time zone is different from the initiator system time zone.
  • Comparisons with DATE in the WHERE clause may yield incorrect results.