Bridge Considerations | Teradata QueryGrid - Single or Multiple Bridge Considerations - Teradata QueryGrid

Teradata® QueryGrid™ Installation and User Guide

Product
Teradata QueryGrid
Release Number
2.19
Published
July 2022
Language
English (United States)
Last Update
2022-07-28
dita:mapPath
jpf1654813554544.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.