- 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
Links are named configurations that include an initiating connector and a target connector. If the same property is set for a link and a connector, the link setting overrides the connector setting.
| Name | Default | Description | Overridable? Property Name |
Connector Type |
|---|---|---|---|---|
| Authentication Mechanism | Trusted | Indicates the authentication mechanism used on the target data source. Values are Trusted, TD2, Kerberos, and LDAP. This is a required setting. |
Target | |
| Byte Count Report Frequency | 64KB | Frequency with which byte count is updated in DBQL. You can adjust this to a larger value if the update frequency is too resource intensive. | ● byteCountReportFrequency |
Initiator, Target |
| Connection Evict Frequency | 30 minutes |
Frequency of eviction checks. Connection objects from the pool are checked, closed, and removed if the idle time (current time - last time of use) of a connection object is greater than the Connection Max Idle Time setting. Reduce the time between checks if there are multiple concurrent users running queries to clear the connections more frequently. Valid values are 1–1440 minutes. |
Target | |
| Connection Max Idle Time | 86400 seconds |
The maximum idle time for the connection cache object, after which the object is closed and removed from the cache. Use this property when there are multiple concurrent users and queries running on the system that might lead to starvation of connection objects. Valid values are 1–86400 seconds. |
Target | |
| Connection Pool Size | 100 |
Maximum number of connection objects that can be stored in a connection pool. When acquiring a new connection, the connector checks for an available space in the pool. If no space is available in the connection pool, the connection fails after 5 minutes. Only one connection pool and username per connector configuration is allowed. Valid values are 1–10000. |
Target | |
| Custom Push Profile | -- | Teradata, Presto, or Hive custom push profile used with the Remote Table Optimization (RTO) feature This custom push profile overrides a default push profile. |
● customPushProfile |
Initiator |
| Default Push Profile | -- | Teradata, Presto, or Hive default push profile used with the Remote Table Optimization (RTO) feature This push profile is used if there is no custom push profile. |
Initiator | |
| Disable Pushdown | False | When set to true, disables the pushdown of all query conditions to the target system. Certain system-level, session-level, and column-level query attributes, such as CASESPECIFIC, can affect character string comparison results. These attributes can cause some queries to return incorrect results due to incorrect row filtering on the target system. To avoid incorrect results caused by condition pushdown in situations where the settings on the initiating system do not match the settings on the target system, you can disable the pushdown of all conditions to the target system. If set to Overridable, this property can only be overridden at the session level from false to true (indicating you are disabling pushdown), but cannot be changed from true to false. |
● disablePushdown |
Initiator |
| Enable Async Abort | False | Indicates if PDE asynchronous abort should be enabled. | Initiator, Target | |
| Enable Logging | None | Logging level for the connector or link properties. User level log settings can be explicitly set through the add or edit link page in the QueryGrid portlet. This setting applies to both the initiating and target connector; however, the logging level for the initiating connector in the link takes precedence if they are set differently. Valid values are NONE, WARN, INFO, DEBUG, and VERBOSE. |
Initiator, Target | |
| Link Buffer Count | 4 | Maximum number of write buffers available on a single channel at one time. Link Buffer Count overrides the default internal fabric property shmDefaultNumMemoryBuffers.
Valid values are 4–8. |
● linkBufferCount |
Initiator, Target |
| Link Buffer Size | 1048576 | Maximum size of the write buffers to allocate for row handling and message exchange. Valid values are 73728– 10240000 bytes. |
● linkBufferSize |
Initiator |
| Link Handshake Timeout | 30000 | Handshake timeout in milliseconds for the link channel setup. Valid values are 5000–300000. |
Initiator, Target | |
| Link Heartbeat Interval | 60000 | Maximum interval in milliseconds for the heartbeat signal on a channel between the connector and the fabric instance, used for health check status. This interval should be greater than Link Handshake Timeout.
Valid values are 5000–300000. |
Initiator, Target | |
| Password | None | User password. Maximum length is 255 characters. |
Target | |
| Port | None | Default value for a Teradata connector is 1025. Valid values are 1026–65535. The default value can be overridden. |
Target | |
| Read Timeout | 300000 | Number of seconds to wait to read between data packets when importing data messages. | ● readTimeout |
Initiator, Target |
| Realm | None | Kerberos realm. | Target | |
| Replace Unsupported Unicode Character | False | Replaces unsupported Unicode characters with U+FFFD, when importing data by a Teradata connector. If you are using Unicode Pass Through characters, do not set this property to true.
See Validate Unsupported Unicode Characters. |
Initiator, Target | |
| Response Timeout | 1800000 | Number of milliseconds to wait for the final data exec response when all the data has been transferred. | ● responseTimeout |
Initiator, Target |
| Role Support | False | Enable user role support for the target system. When set to true, the user role from the initiator or target based on role mapping is applied to the target system and any errors are returned back to the user. When set to false, roles are not applied to the target system. | ● roleSupport |
Target |
| Server | None | Used to connect to the target database as part of the JDBC connection string. This is the IP address or DNS name of the target host. | Target | |
| Temporary Database Name | None | Specified database name for creating temporary tables/views. If you do not provide a database name in this property, QueryGrid creates the temporary view in the default database assigned to the user. |
● tempDbName |
Target |
| Teradata GSS JAR Path | /usr/tdbms/bin/tdgssconfig.jar | Specifies the absolute path (gssJar) to the Teradata GSS JAR file (tdgssconfig.jar) to use for the JDBC connection of a target connector. | ||
| Teradata JDBC JAR Path | /usr/tdbms/bin/terajdbc4.jar | Specifies the absolute path (jdbcJar) to the Teradata JDBC JAR file (terajdbc4.jar) to use for the JDBC connection of a target connector. | ||
| Username | Default username for the connector. For the Teradata connector, the default is DBC. | Name of the user. Maximum length is 255 characters. This NVP is saved in the Teradata QueryGrid Manager configuration and is required when the initiator does not support a mechanism to provide user credentials. The username is also used for connectivity diagnostic checks. |
Target | |
| Validate Unsupported Unicode Characters | False | Validate unsupported Unicode character when importing data by a Teradata connector. If you are using Unicode Pass Through characters, do not set this property to true.
See Replace Unsupported Unicode Character. |
Initiator, Target | |
| Write Timeout | 300000 | Number of milliseconds to wait to write between data packets when exporting data messages. | ● writeTimeout |
Initiator, Target |