| Info |
|---|
The Teradata Execute action plugin is available in the Hub. |
...
Used this action when you want to run a Teradata command before or after a data pipeline. For example, you might want to run an SQLl SQL update command on a database before the pipeline source pulls data from tables.
Configuration
Property | Macro Enabled? | Description |
|---|---|---|
Driver Name | No | Required. Name of the JDBC driver to use. Default is teradata. |
Host | Yes | Required. Database command to execute. Default is localhost. |
Port | Yes | Required. Host that Teradata is running on. Default is 1025. |
Database | Yes | Required. Port that Teradata is running on. |
Database Command | Yes | Required. Teradata database name. |
Username | Yes | Optional. User identity for connecting to the specified database. |
Password | Yes | Optional. Password to use to connect to the specified database. |
Connection Arguments | Yes | Optional. A list of arbitrary string key/value pairs as connection arguments. These arguments will be passed to the JDBC driver as connection arguments for JDBC drivers that may need additional configurations. |
Example
Suppose you want to execute a query against a Teradata database named “prod” that is running on “localhost” port 1025 (Ensure that the driver for Teradata is installed. You can also provide driver name for some specific driver, otherwise “teradata” will be used), and then configure the plugin with:
Property | Value |
|---|---|
Driver Name |
|
Database Command |
|
Host |
|
Port |
|
Database |
|
Username |
|
Password |
|