...
Data Definition Language (DDL) queries
Data Manipulation Language (DML) queries
Data Control Language (DCL) queries
This Snap works only with single queries.
The Snap runs each statement as a single atomic unit so as to allow rolling back changes when a statement fails during its execution.
...
Known Issues
None.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| Input document is not mandatory. The Snap can fetch and apply values for parameterized queries from an upstream Snap output. |
Output | Document |
|
| A JSON document containing each SQL statement along with its execution status (or result). |
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 while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:
Learn more about Error handling in Pipelines. |
Snap Settings
Info |
---|
|
Field Name | Field Type | Description | |
---|---|---|---|
Label* Default Value: Databricks - Execute | String | The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline. | |
SQL Statements* | Use this fieldset to define your SQL statements, one in each row. You can add as many SQL statements as you need. | ||
SQL statement* Default Value: None. | String/Expression | Specify the Databricks SQL statement you want the Snap to execute. We recommend you to add a single query in the SQL Statement field. The SQL statement must follow the SQL syntax as stipulated in DLP. | |
Number of Retries Default Value: 0 Minimum value: 0
| Integer | Specify the maximum number of retry attempts the Snap must make in case there is a network failure and is unable to read the target file. The request is terminated if the attempts do not result in a response.
|
Ensure that the local drive has sufficient free disk space to store the temporary local file. | |||||
Retry Interval (Seconds) Default value: 1 Minimum value: 1
| Integer | Specify the minimum number of seconds the Snap must wait before each retry attempt. | |||
Use Result Query | Checkbox | Select this checkbox to write the SQL statement execution result to the Snap's output view for each successful execution. The output of the Snap is enclosed in the key This option allows you to effectively track the SQL statement's execution by clearly indicating the successful execution and the number of records affected, if any, after the execution. For DDL statements Because the Databricks JDBC driver does not return a result set for Data Definition Language (DDL) statements such as DROP, CREATE, and ALTER, the Snap displays a standard message: | |||
Manage Queued Queries Default Value: Continue to execute queued queries when pipeline is stopped or if it fails. | Dropdown list | Select either of the following options from the dropdown list to handle queued SQL queries:
If you select Cancel queued queries when pipeline is stopped or if it fails, then the read queries under execution are cancelled, whereas the write type of queries under execution are not cancelled. Databricks internally determines which queries are safe to be cancelled and cancels those queries.
| |||
Snap Execution Default Value: Execute only | Dropdown list | Select one of the three modes in which the Snap executes. Available options are:
|
Troubleshooting
Error | Reason | Resolution |
---|---|---|
Missing property value | You have not specified a value for the required field where this message appears. | Ensure that you specify valid values for all required fields. |
Examples
Replacing old data in a DLP table with the latest data
...
Downloads
Info |
---|
|
Attachments | ||||||
---|---|---|---|---|---|---|
|
...