...
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 | Yes | Required. Name of the JDBC driver to use. Default is db211. |
Host | Yes | Required. Host that DB2 is running on. Default is localhost. |
Port | Yes | Required. Port that DB2 is listening to. Default is 50000. |
Database | Yes | Required. DB2 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 | 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, if the pipeline completes successfully, you want to delete all records from DB2 table "userEvents" of database "prod" running on "localhost", port 50000, without authentication using driver "db211" if the pipeline completes successfully (Ensure . First, ensure that the driver for DB2 is installed. You can also driver name for some specific driver, otherwise "db211" will be used ), and then configure the plugin with:
Property | Value |
---|---|
Driver Name |
|
Host |
|
Port |
|
Database |
|
Query |
|