Actions for Snowflake #
-
Send Data. Sends a custom set of Lucidum data to SnowFlake.
Use Cases #
Below are the possible use cases for the Send Data action:
-
If you want to run Lucidum “headless”, you can send relevant data to Snowflake on a regular schedule.
-
You can send data to Snowflake for storage and analysis.
Workflows #
- Creating a new Configuration and a new Action
- Cloning an Existing Action
- Creating a new Action from the Location Results page
- Editing a Configuration
- Editing an Action
- Viewing Information about an Action
Snowflake Configuration #
To create the Snowflake configuration, enter values in the following fields:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
-
Account ID. The Snowflake account ID. Of the format account locator.cloud region. For details on viewing your account locator and cloud regions, see https://docs.snowflake.com/en/user-guide/admin-account-identifier#finding-the-region-and-locator-for-an-account.
-
User name. The user name for a user account that has read and write permissions in Snowflake.
-
Password. The password associated with User Name.
- Role. Role for the user in User Name. The role must allow USAGE on Swowflake databases and schemas where you want to send Lucidum Data. The role must also include SELECT, INSERT, UPDATE, on all tables in databases.
-
Max # of Records per Insert. The maximum number of Snoflake records that can be created or updated with a single execution of the action.
Create or Edit an Action #
To create an action for Snowflake:
-
In the Create a New Action page, in the General step, enter:
-
Action Type. Select an action from the pulldown options.
-
Configuration Name. Select an action configuration from the pulldown options.
-
Action Name. Identifier for the action. This name will appear in the Lucidum Action Center.
-
Description. Description of the action.
-
-
Click the Next (>) icon.
-
In the Filters page, click Configure Filters.
-
The Build a Query page appears.
- In the Build a Current Query page, enter the fields, operators, and values for the query. For existing actions, the query is already loaded in this page.
- For details on creating and editing queries in Lucidum, see the section on Building Queries.
NOTE: To optimize performance, the default time range is Current. If you need to access historical data, contact Lucidum Custom Success for help on using historical data without affecting performance.
-
Click the Apply (page and pencil) icon.
-
Click the Next (>) icon.
-
In the Schedule step, enter:
-
Schedule Type. Define the schedule for the action. Choices are:
-
Recurrence. Specify a frequency for the recurring schedule.
-
After Data Ingestion. The action is executed after data ingestion, which happens at least once every 24 hours and can also be triggered manually.
-
-
Do not trigger the action unless. Specify the number of results from Filters as a prerequisite for executing the action.
-
-
Click the Next (>) icon.
-
The Details page defines the data load you want to send to Snowflake. Enter the following in the Details step:
-
Output Fields. For the records selected with the Filters field, specify the columns to display. To see the fields, return to the Filters page and click Configure Filters. In the Build Query page, click the Show Results (page) icon. In the Query Results page, click the Column icon to see a list of all fields included in the query results.
-
Snowflake Target Warehouse Name. A warehouse provides the required resources, such as CPU, memory, and temporary storage, to perform operations in a Snowflake session.
-
Snowflake Target Database Name.
-
Snowflake Target Table Name.
-
Dedupe Previous Jobs. In this field, you specify whether you want duplicates of asset IDs (if your query is for assets) or user IDs (if your query is for users). You can specify integers starting at 0 (zero).
-
If you specify “0” (zero), Lucidum includes all the records from the query in each delivery to Snowflake.
-
If you specify “1” (one), Lucidum examines the previous payload and excludes records for asset IDs or user IDs that were sent in the previous delivery to Snowflake.
-
If you specify “2” (two), Lucidum examines the last two payloads and excludes records for asset IDs or user IDs that were sent in the previous two deliveries to SnowFlake.
-
-