A Vantage customer is using the Hive Connector in QueryGrid to access a foreign server and push the processing onto the Hadoop Cluster. The Vantage…

When using Teradata QueryGrid with pushdown processing to a foreign server like Hadoop/Hive, temporary space is consumed on both the Vantage system and the foreign system. On the Vantage side, intermediate or final result sets returned from the foreign server consume the user's spool space. On the Hadoop/Hive side, complex operations that are pushed down may require the creation of temporary tables. The location for these temporary tables is specified by the temporary database name property within the QueryGrid link definition. An administrator concerned about performance and space consumption must investigate both of these aspects to manage resources effectively.

A. Perm space assigned to the user executing the QueryGrid query

Perm space is used for storing permanent database objects like tables, not for temporary data generated during query execution.

B. The default temporary NOS location defined on the connector

NOS (Native Object Store) locations are for reading data from object stores like S3 or ADLS. This is not the primary mechanism for managing temporary tables on a Hadoop cluster for Hive pushdown processing.

D. Temp space assigned to the Teradata user defined in the authorization object

Temp space in Teradata is reserved for Global Temporary Tables (GTTs). Standard query processing and intermediate results use spool space, making spool the relevant resource to investigate, not temp space.

---

1. Teradata® QueryGrid™ Installation and User Guide (Release 17.10, B035-5800-0122K)

Section: "Link Properties" (Chapter 3: Using QueryGrid). This section details the configuration properties for connectors. For connectors that support pushdown, it describes the TEMPORARYDATABASE or equivalent property. It states, "For connectors that support pushdown of extended SQL, you can specify a remote database or schema for QueryGrid to create temporary tables." This confirms the need to investigate the temporary database name on the link.

Section: "QueryGrid Processing" (Chapter 1: Introduction to Teradata QueryGrid). The documentation explains that when results are returned to Vantage or when parts of the query cannot be pushed down, the data is processed on the AMPs and consumes the user's spool space. This validates the "spool space" part of the answer.

2. Teradata Vantage™ Database Administration (Release 17.10, B035-1093-171K)

Chapter 12: Managing Space. This chapter defines the different types of space. Specifically, it describes Spool Space as "a temporary workspace for the results of SQL queries" and distinguishes it from Perm Space (for permanent data) and Temp Space (for global temporary tables), confirming that spool is the correct space to consider for query execution.