| Connector Type | Description |
|---|---|
| Initiating | Point from which a Teradata Fabric query originates. For example, in a Teradata-to-Hive query, the Teradata connector initiates the query. |
| Target | Destination point of a Teradata Fabric query. For example, in a Teradata-to-Hive query, a Hive connector is the target connector that the initiating connector accesses to either import or export data. |
| Connectors Defined | Result |
|---|---|
| Teradata systems only | You can create links only between Teradata systems. |
| Teradata, Hive, Spark, Oracle, BigQuery, Arrow Flight SQL, and Generic JDBC | You can create links between Teradata systems with any of these connector types. |
Links simplify configuration of foreign server definitions in preparation for running Teradata Fabric queries.
- An initiating connector and a target connector link pairing to use for queries
- The number of bridges used, if any:
Number of Bridges Number of Hops Defined No bridge One hop (the hop between the initiator and target) One bridge Two hops (the hop between the initiator and bridge, and the hop between the bridge and target) Two bridges Three hops (the hop between the initiator and the first bridge, the hop between the first bridge and second bridge, and the hop between the second bridge and target) Three bridges Four hops (the hop between the initiator and the first bridge, the hop between the first bridge and second bridge, the hop between the second bridge and third bridge, and the hop between the third bridge and target). Four bridges Five hops (the hop between the initiator and the first bridge, the hop between the first bridge and second bridge, the hop between the second bridge and third bridge, the hop between the third bridge and fourth bridge, and the hop between the fourth bridge and target). - The properties of the initiating and target connectorsWhen you create links and associated properties, you are creating Configuration Name Value Pairs (NVP). An NVP does the following:
- Specifies the behavior of the target connector component
- Configures how data is transformed
- Configures the underlying link data transportation layer
- Affects how the initiator connector performs
Optional properties allow for configuration refinement of the initiating or target connector. These link properties override connector properties.
- Define initiating and target networks for hops
- Links refer to networks to determine which interfaces to use for data transfer. A query originates in a certain server or network and is sent to a target server or network. If no network is specified, the fabric tries all known target node network addresses in parallel and uses the first address that successfully establishes a connection.
- Networks are defined by rules that map physical network interfaces to logical network definitions, either by interface name or by Classless Inter-Domain Routing (CIDR) notation. The rules are checked in the order they appear in a matching rules list.
- A communications policy that defines rules for transferring data between target and initiating connectors and bridges (if used)
Communication policies define how systems communicate with one another. They allow you to configure the transfer concurrency and enable or disable ZStandard data compression on row data blocks during data transfer.
Teradata Fabric is preconfigured with a Communication Policy with compression enabled (Compression) and one without compression enabled (No Compression).
Communication policies are not necessarily specific to the systems involved, so you can reuse them.
- User mappings (optional)
User mappings allow a user logged on to the initiating system to submit queries as a specific user on the target system. You can map multiple users on the initiating system to a single user on the target system, if applicable, but you cannot map multiple users on the target system to a single user on the initiating system.
In the Teradata Fabric portlet, you can map usernames on one data source to usernames on another data source.
When using the Hive or Spark target connector without security, user mapping is typically required. For example, if a query is initiated using a Teradata-to-Hive link by user Joe, Teradata automatically changes the username to all uppercase and sends the query as user "JOE" by default to the target system. The following are possible outcomes for this use-case when no security is used with a Hive target connector:Scenario Requirement User "JOE" does not exist on the target system Queries must be run with an existing user on the target system such as "hive". In this scenario, user mapping is required where "JOE" on the Teradata system is mapped to the user "hive" on the target Hive system. Does exist on the target system as joe User mapping is required where "JOE" on the Teradata system is mapped to "joe" on the target Hive system. Does exist on the target as "JOE" This scenario does not require user mapping. When a security platform such as Kerberos is used, user mapping is not required when using a Hive or Spark target connector.
- Enable or disable acknowledgments. Acknowledgments allow Teradata Fabric to reestablish connections that break due to transient network errors. If queries fail due to network errors, this option can be enabled at the expense of slightly more message overhead.