Generic JDBC - Execute
In this article
Overview
You can use this Snap to execute a SQL statement/query against a SQL database. This Snap also supports DCL commands (Grant and Revoke).
This Snap works only with single queries.
This Snap only supports conversion of standard JDBC specification 4.1 types listed here. Learn more about the JDBC 4.1 specification. If you want database-specific conversion, then a database specific Snap pack should be used. For example, for handling TIMESTAMPTZ and TIMESTAMPLTZ formats, you should use the Oracle Snap Pack.
The Generic JDBC Execute Snap is used for simple DDL (SELECT, INSERT, UPDATE, DELETE) type statements. This Snap also supports DML operations (CREATE, ALTER, INSERT, and SELECT) when using AWS Athena database.
Snap Type
The Generic JDBC - Execute Snap is a WRITE-type Snap that writes the results of the executed JDBC queries.
Prerequisites
None.
Support for Ultra Pipelines
Works in Ultra Pipelines.
Known Issues
If a
SELECT
query in the SQL statement field in the Snap Settings contains duplicate column names, then the query result displays the column name twice, with the latter prefixed with the table name. If the column name occurs more than twice, the second entry is still prefixed with the table name, but it displays the value of the column mentioned last in the query. The example below illustrates this behavior.
The metadata output in the second output preview is not displayed in table format when your target database is AWS Athena.
The suggestions list is not populated for Table name field when your target database is AWS Athena.
When the SQL statement property is an expression, the Pipeline parameters are shown in the suggest, but not the input schema.
When the Generic JDBC—Execute Snap connects to the Sybase database to retrieve
BigTime
-type data, the Snap displays both date and time for the data type.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| The input data typically includes the SQL query that you want to execute on your database. The specific format of the input data can vary depending on the design of your pipeline and the data source you are using, but typically it can be the SQL query. In addition to the SQL query, you may also need to provide additional parameters that need to be substituted in the query. |
Output | Document
|
|
| If an output view is available and an update/insert/merge/delete statement was executed, then the original document that was used to create the statement will be output with the status of the executed statement. |
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Learn more about Error handling in Pipelines. |
Snap Settings
Asterisk ( * ): Indicates a mandatory field.
Suggestion icon (