Configuring Vertica Accounts
On this Page
This account is used by the Snaps in the Vertica Snap Pack.
You can create an account from Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:
- Your private project folder: This folder contains the pipelines that will use the account.
- Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
- The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.
Account Configuration
In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for Vertica:
- Click Create, then select Vertica > Vertica Database Account.
- Supply an account label.
- Supply the required account properties such as Hostname, Port number, Database name. Upload the appropriate JDBC driver and specify the JDBC driver class.
- (Optional) Supply additional information on this account in the Notes field of the Info tab.
- Click Apply.
Avoid changing account credentials while pipelines using them are in progress. This may lead to unexpected results, including locking the account.
Account Types
Vertica Database Account
Account Settings
Label | Required. User provided label for the account instance | |
|---|---|---|
Account properties | Required. Enter in the information to create a connection to the database. | |
Hostname | Required. The server's address to connect to. Default value: [None] | |
Port Number | Required. The database server's port to connect to. Default value: 3306 | |
Database name | Required. The database name to connect to. Default value: [None] | |
Username | Username that is allowed to connect to the database. Username will be used as the default username when retrieving connections. The username must be valid in order to set up the data source. Default value: [None] | |
Password | Password used to connect to the data source. Password wil be used as the default password when retrieving connections. The password must be valid in order to set up the data source. Default value: [None] | |
JDBC jars | Select the JDBC driver to use. A different driver binary for a driver must have a different name, the same name can not be reused for a different driver. If this property is left blank, a default JDBC driver will be loaded. Default value: shared/Vertica-6.1.0.jar | |
JDBC Driver Class | Required. JBDC driver class name to use. Default value: com.vertica.jdbc.Driver | |
| Advanced properties | ||
Auto commit | When selected, each of the batches is committed immediately after it is executed. If the Snap fails, only the batch being executed at that moment is rolled back. When deselected, the Snap execution output is committed only after all the batches are executed. If the Snap fails, the entire transaction is rolled back, unless the Snap finds invalid input data before it sends the insert request to the server, and routes the error documents to the Error view. Default value: Selected | |
Batch size | Required. Number of statements to execute at a time. Select queries are not batched. Using a large batch size could use up the JDBC placeholder limit of 2100. Default value: 50 | |
Fetch size | Required. Number of rows to fetch at a time when executing a query. Large values could cause the server to run out of memory. Default value: 100 | |
Min pool size | Required. Minimum number of connections a pool will maintain at a time. Default value: 3 | |
Max pool size | Required. Maximum number of connections a pool will maintain at a time. Default value: 50 | |
Max life time | Required. Maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed. Default value: 30 | |
Idle Timeout | Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool. Default value: 5 | |
Checkout timeout | Required. Number of milliseconds to wait for a connection to be available when the pool is exhausted. Zero waits forever. An exception will be thrown after the wait time has expired. If you provide 0, the Snap waits infinitely until the connection is available. Therefore, we recommend you not to specify 0 for Checkout Timeout. Default value: 10000 | |
| URL properties | ||
URL property name | URL property name Default value: [None] | |
URL property value | URL property value Default value: [None] | |
Account Encryption
| Standard Encryption | If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed. | |
|---|---|---|
| Enhanced Encryption | If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account. Account:
| |
Auto Commit with Execute Snaps
For a DB Execute Snap, assume that a stream of documents enters the input view of the Snap and the SQL statement property has JSON paths in the WHERE clause. If the number of documents are large, the Snap executes in more than one batches rather than executing one per each document. Each batch would contain a certain number of WHERE clause values. If Auto commit is turned on, a failure would only roll back the records in the current batch. If Auto commit is turned off, the entire operation would be rolled back. For a single execute statement (with no input view), the setting has no practical effect.
Snap Pack History
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.