Bridge Considerations | Teradata QueryGrid - Single or Multiple Bridge Considerations - 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
Use a bridge configuration when direct connectivity is not available between initiating and target data source systems. One or two bridge systems can be included in the data transfer path between data source nodes in initiator and target systems. The following defines nodes in a bridge system:
  • A subset of data source nodes running QueryGrid node software. The data source nodes can be in the initiator system, target system, or both.
  • A set of non-data source nodes running QueryGrid node software. The non-data source nodes do not need connector software because they do not have local data to process.

    An example of a non-data source node is an edge node in a Hadoop system.

Multiple bridge nodes are recommended per bridge system so if a bridge node goes offline, QueryGrid queries can continue to be submitted.