Teradata Query Post-run Action

The Teradata Query Post-run action plugin is available in the Hub.

Runs a Teradata query at the end of the pipeline run. Can be configured to run only on success, only on failure, or always at the end of the run.

The action is used whenever you need to run a query at the end of a pipeline run. For example, you may have a pipeline that imports data from a database table to HDFS files. At the end of the run, you may want to run a query that deletes the data that was read from the table.

Configuration

Property

Macro Enabled?

Description

Property

Macro Enabled?

Description

Run Condition

Yes

Optional. When to run the action. Must be 'completion', 'success', or 'failure'. Defaults to 'success'. If set to 'completion', the action will be executed regardless of whether the pipeline run succeeded or failed. If set to 'success', the action will only be executed if the pipeline run succeeded. If set to 'failure', the action will only be executed if the pipeline run failed.

Default is success.

Driver Name

No

Required. Name of the JDBC driver to use.

Default is teradata.

Host

Yes

Required. Host that Teradata is running on.

Default is localhost.

Port

Yes

Required. Port that Teradata is running on.

Default is 1025.

Database

Yes

Required. Teradata database name.

Query

Yes

Required. Query to run.

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 delete all records from Teradata table "userEvents" of database "prod" running on localhost, port 1025, without authentication using driver "teradata" if the pipeline completes successfully (Ensure that the driver for Teradata is installed. You can also driver name for some specific driver, otherwise "teradata" will be used ), and then configure the plugin with:

Property

Description

Property

Description

Run Condition

success

Driver Name

teradata

Query

delete * from userEvents

Host

localhost

Port

1025

Database

prod

Username

dbc

Password

dbc