Configuring Cassandra Accounts
This page is no longer maintained (Nov 12, 2025). For the most current information, go to Configuring Cassandra Accounts.
On this Page
This account is used by the Snaps in the Cassandra 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 Cassandra:
Click Create, then select Cassandra
Choose an account:
Cassandra Database Account
Cassandra SSL/TLS Database Account
Supply an account label.
Supply the necessary account properties for your database.
Supply the Username, Password (Only if you opt for Cassandra Database Account).
Supply the Port and Database name.
(Optional) Supply additional information on this account in the Notes field of the Info tab.
Click Apply
Enabled expressions for required fields to support dynamic account.
Avoid changing account credentials while pipelines using them are in progress. This may lead to unexpected results, including locking the account.
Account Types
Cassandra Database Account
Cassandra SSL/TLS Database Account
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.
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2026 SnapLogic, Inc.