Skip to content

Snowflake

Snowflake is a leading cloud-based data warehousing platform renowned for its scalable and high-performance capabilities, allowing organizations to manage and analyze large volumes of data efficiently. When used in conjunction with Martini Runtime an advanced execution environment optimized for data-intensive tasks Snowflake's capabilities are further enhanced, providing a robust solution for complex data processing. This combination facilitates streamlined workflows and high-performance analytics, ensuring that data operations are both scalable and cost-effective, and making it easier to handle real-time analytics and large-scale data tasks within a unified and optimized environment.

Configuring Snowflake

Configuring Snowflake with Martini Runtime involves integrating Snowflake’s cloud-based data warehousing capabilities with Martini Runtime’s advanced execution environment to optimize data processing and analytics workflows. Start by setting up your Snowflake environment with necessary warehouses, databases, and schemas to organize and manage your data. Then, configure Martini Runtime to handle data-intensive tasks and workflows, ensuring it can efficiently process and execute complex data operations. Here’s a straightforward guide to adding a new database connection:

Configuration Guide

Via API Explorer: Database connections can be configured using the Martini API Explorer, a user-friendly interface designed for efficient interaction with the system's APIs. Follow these steps to configure the database connections through the API Explorer:

  1. Access the API Explorer: Open a web browser and go to [HOST]:8080/api-explorer/ to access the API Explorer.

  2. Navigate to the Database Tag: Locate and click on the database tag within the API Explorer to view various database configuration and operation endpoints.

  3. Configure Connection Pool: Use the esbapi/databases endpoint found under the database tag to save a database connection pool.

  4. Use POST to Save a Connection Pool: Save the connection pool by using the POST method at the /esbapi/databases endpoint. Here is a minimum requirement for a JSON payload: 

    1
2
3
4
5
6
7
8
     {
     "name": "[name]",
     "type": "jdbc",
     "url": "[accountID].snowflakecomputing.com/?[ConnectionParameter]",
     "driverClassName": "net.snowflake.client.jdbc.SnowflakeDriver", 
     "username": "[username]",
     "password": "[password]" 
 }

Via File System: Alternatively, database connections can be modified directly in the file system by editing the <name>.dbxml file located in the /<martini-home>/conf/db-pool/ directory. The <name>.dbxml file refers to the specific file for your database configuration. This method is particularly useful in environments with restricted API access or during initial setup stages.

To modify database connections directly through the file system, follow these steps:

  1. Locate the Configuration File: Navigate to the /<martini-home>/conf/db-pool/ directory on your server and locate the <name>.dbxml file.

  2. Edit the Database Connections: Open the <name>.dbxml file in a text editor and modify the database connection properties.

  3. Save and Restart: After making the desired changes, save the file. It is essential to restart the Martini Runtime instance to apply the new settings. This ensures that all components of the application use the updated JDBC configuration. Here is a minimum requirement for a dbXML: 

    1
2
3
4
5
6
7
8
     <database>
     <name>[name]</name>
     <type>jdbc</type>
     <url>[accountID].snowflakecomputing.com/?[ConnectionParameter]</url>
     <driverClassName>net.snowflake.client.jdbc.SnowflakeDriver</driverClassName> 
     <username>[username]</username>
     <password>[password]</password>
 </database>

Connection Properties

For more details on constructing a JDBC connection URL for Snowflake, you can refer to the official documentation: JDBC Driver connection parameter reference.

Database Properties

These properties include various settings that control the operation of the database. For detailed information on configuring these settings, refer to the JDBC database properties documentation.