- Provide query processing across data sources (systems).
- Translate query request SQL from one source query format to another.
- Transform data, converting the data from one data type or format to another so that the data can be exchanged between different data source systems.
- Enable data sources to participate in queries. Any connector that joins the fabric can participate in the queries.
- Enable data sources to initiate queries.
- Except for the Oracle, BigQuery, Arrow Flight SQL, and Generic JDBC connectors.
- Enable sending and receiving data to and from the fabric.
- Communicate with other connectors in the fabric.
- Control the running of queries on target systems. All connectors can act as a target of queries and control the queries that run on a target data source system on behalf of the initiator data source system.
- Return query results to initiating systems.
Connectors are specific to the system type (for example, Teradata systems, Hive, or Oracle). For instance, Teradata system hosts a Teradata connector, but a single Hadoop system can host multiple connectors (for example, Hive and Spark).
Optional connector properties allow you to refine a connector type configuration or override connector properties set during configuration.
Connector software connects data sources with the data analytics fabric. The software is installed on all data source nodes in a system. Fabric software is also installed on all data source nodes in a system. Fabric software includes a driver. A driver runs on one or more data source nodes called driver nodes. As part of query processing, a driver node receives requests from the initiator connector and submits the requests to the target system. The driver loads the connector, reads messages, invokes methods to process requests, and sends responses.
- Specify which nodes in a data source are driver nodes.
Only a subset of the nodes on a large system need to be driver nodes.
- Select multiple driver nodes for redundancy and to share the workload required for query initiation.
- Limit the number of driver nodes to enable better session reuse.
- Reuses physical connections
- Reduces overhead for Teradata Fabric queries
- Minimizes creating and closing sessions
The connection pool uses the same JDBC connection for all phases of a single query or for subsequent queries with the same session and user credentials. For information on configuring tunable connector pool properties, see the connector and link properties information for the relevant connector.