SAP HANA - Execute
On this Page
Snap type | Write | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Description | This Snap allows you to execute arbitrary SQL. This Snap works only with single queries. You can drop your database with it, so be careful. Valid JSON paths that are defined in the where clause for queries/statements will be substituted with values from an incoming document. Documents will be written to the error view if the document is missing a value to be substituted into the query/statement. If a SELECT query is executed, the query's results are merged into the incoming document and any existing keys will have their values overwritten. On the other hand, the original document is written if there are no results from the query.
The SAP HANA Execute Snap is for simple DML (SELECT, INSERT, UPDATE, DELETE) type statements. For the comprehensive scripting functionality offered by the various databases, users should use stored procedure functionality offered by their chosen database in the Stored Procedure Snap. | ||||||||||
| Prerequisites | [None] | ||||||||||
| Support and limitations | Works in Ultra Task Pipelines. | ||||||||||
| Behavior Change |
If you have any existing Pipelines that are mapped with status key or previous description then those Pipelines will fail. So, you might need to revisit your Pipeline design. | ||||||||||
| Account | This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Configuring SAP HANA Accounts for information on setting up this type of account. | ||||||||||
| Views |
| ||||||||||
Settings | |||||||||||
Label* | Specify 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 statement | Specify the SQL statement to execute on the server. Scenarios to successfully execute your SQL statements Scenario 1: Executing SQL statements without expressions
Examples:
Additionally, the JSON path is allowed only in the WHERE clause. If the SQL statement starts with SELECT (case-insensitive), the Snap regards it as a select-type query and executes once per input document. If not, it regards it as write-type query and executes in batch mode. Scenario 2: Executing SQL queries with expressions
Table name and column names must not be provided as bind parameters. Only values can be provided as bind parameters. Examples:
We recommend you to add a single query in the SQL Statement field. Known Issue When the SQL statement property is an expression, the pipeline parameters are shown in the suggest, but not the input schema.
Single quotes in values must be escaped Any relational database (RDBMS) treats single quotes ( For example:
Default Value: [None] | ||||||||||
| Query type | Select the type of query for your SQL statement (Read or Write). When Auto is selected, the Snap tries to determine the query type automatically. Default Value: Auto | ||||||||||
Pass through | Select this checkbox to pass the input document to the output view under the key 'original'. This property applies only to the Execute Snaps with SELECT statement. Default Value: Selected | ||||||||||
Ignore empty result | Select this checkbox to ignore empty result; no document will be written to the output view when a SELECT operation does not produce any result. Default Value: Not selected | ||||||||||
Auto commit | Select one of the options for this property to override the state of the Auto commit property on the account. The Auto commit at the Snap-level has three values: True, False, and Use account setting. The expected functionality for these modes are:
Default Value: Use account setting 'Auto commit' may be enabled for certain use cases if PostgreSQL jdbc driver is used in either Redshift, PostgreSQL or generic JDBC Snap. But the JDBC driver may cause out of memory issues when Select statements are executed. In those cases, “Auto commit" in Snap property should be set to ‘False’ and the Fetch size in the “Account setting" can be increased for optimal performance. Behavior of DML Queries in Database Execute Snap when auto-commit is false DDL queries used in the Database Execute Snap will be committed by the Database itself, regardless of the Auto-commit setting. When Auto commit is set to false for the DML queries, the commit is called at the end of the Snap's execution. The Auto commit needs to be true in a scenario where the downstream Snap does depend on the data processed on an Upstream Database Execute Snap containing a DML query. When the Auto commit is set to the Use account setting on the Snap, the account level commit needs to be enabled. | ||||||||||
| Number of retries | Specify the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response. Default Value: 0 Ensure that the local drive has sufficient free disk space to store the temporary local file. | ||||||||||
| Retry interval (seconds) | Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. Default Value: 1 | ||||||||||
Snap execution | Select one of the three modes in which the Snap executes. Available options are:
| ||||||||||
.png?version=1&modificationDate=1489744290984&cacheVersion=1&api=v2)
.png?version=1&modificationDate=1489744292055&cacheVersion=1&api=v2)
Examples
In this example, we have a table named USER that stores user details. It has 3 columns: NAME, AGE and CITY. We will execute the query and retrieve users with age 60 with this pipeline.
.png?version=1&modificationDate=1489746255911&cacheVersion=1&api=v2)
We need to provide the query used to pull the data from USER table in SQL statement property. We will provide dynamic variable values from upstream Snap JSON Generator.
Sample output looks like below:
.png?version=1&modificationDate=1489746253683&cacheVersion=1&api=v2&width=554&height=249)
Snap Pack History
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.