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

Teradata® Fabric - Installation and User Guide - 3.11

Product
Teradata Fabric
Release Number
3.11
Published
August 2026
ft:locale
en-US
ft:lastEdition
2026-08-15
dita:mapPath
svw1780362788070.ditamap
dita:ditavalPath
ezw1784752870623.ditaval
dita:id
lxg1591800469257
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 Teradata Fabric node software. The data source nodes can be in the initiator system, target system, or both.
  • A set of non-data source nodes running Teradata Fabric 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, Teradata Fabric queries can continue to be submitted.