Incremental Package

The Coalesce Base Node Types Package includes:

• Incremental load
• Looped Load
• Run view
• Incremental load Code
• Looped Load Code
• Run view code

Incremental Load

The Coalesce Incremental load node is a versatile node that allows you to develop and deploy a Stage table/view in Snowflake where we can perform incremental load in comparison with a persistent table added on top of it.

Incremental Load Node Configuration

The Incremental node type has two configuration groups:

• Node Properties
• Options

Go to the node and select the config tab to see the Node Properties and Options.

Incremental Load Node Properties

There are four configs within the Node Properties group.

• Storage Location: Storage Location where the WORK will be created.
• Node Type: Name of template used to create node objects.
• Description: A description of the node's purpose.
• Deploy Enabled:
• If TRUE the node will be deployed / redeployed when changes are detected.
• If FALSE the node will not be deployed or will be dropped during redeployment.

Incremental Load Options

• Create As: Provides option to choose materialization type as table or view.

• Filter data based on Persistent table: True / False toggle that helps to load incremental load

• True - provides option to perform incremnetal load.

• False - a normal initial load of data from source is done.
• Persistent table location(required): The Coalesce storage location.
• Persistent table name(required): The table name of the persistent table.
• Incremental load column(date): A date column based on which incremental data is loaded.

Incremental Load Example Workflow

1. Add a source node.
2. Add the Incremental UDN.
3. Leave the 'Filter data based on Persistent Table' option set too false.
4. Create the node.
5. Add the Persistent table to the view.
6. Create and Run the node.
7. Go to the Incremental UDN and change the 'Filter data based on Persistent Table' option to true.
8. Use the pattern based option to match the persistent table (alter the definition of the UDN, if necessary), or add the table name manually in the last config item.
9. Remove the existing (basic) join and use the 'Copy To Editor' to add the new join, including sub-select.
10. Re-run the Incremental UDN.

Incremental Load Deployment

Incremental Load Initial Deployment

When deployed for the first time into an environment the Incremental load node of materialization type table will execute the Create State Table.

• Create Stage Table: This will execute a CREATE OR REPLACE statement and create a table in the target environment. When deployed for the first time into an environment the Work node of materialization type view will execute the Create Stage View.
• Create Stage View: This will execute a CREATE OR REPLACE statement and create a view in the target environment.

Incremental Load Redeployment

After the Incremental Load has been deployed for the first time into a target environment, subsequent deployments with column level changes or table level changes may result in altering the target Table.

Incremental Load Altering the Stage Tables

There are few column or table changes if made in isolation or all-together will result in an ALTER statement to modify the Work Table in the target environment.

• Changing the table name
• Dropping an existing column
• Altering Column data type
• Adding a new column

The following stages are executed:

• Clone Table - Creates an internal table.
• Rename Table | Alter Column| Delete Column | Add Column | Edit table description|: Alter table statement is executed to perform the alter operation.
• Swap cloned Table - Upon successful completion of all updates, the clone replaces the main table ensuring that no data is lost.
• Delete Table - Drops the internal table.

Incremental Load Recreating the Stage Views

The subsequent deployment of Incremental load node of materialization type view with changes in view definition,adding table description or renaming view results in deleting the existing view and recreating the view

The following stages are executed:

• Delete View
• Create View

Incremental Load Undeployment

If a Incremental load node of materialization type table is deleted from a Workspace, that Workspace is committed to Git and that commit deployed to a higher level environment then the stage table in the target environment will be dropped.

This is executed in two stages:

• Delete Table: Coalesce Internal table is dropped.
• Delete Table: Target table in Snowflake is dropped.

If a Incremental load node of materialization type view is deleted from a Workspace, that Workspace is committed to Git and that commit deployed to a higher level environment then the StageView in the target environment will be dropped.

The stage executed:

• Delete View: Drops the existing stage view from target environment.

Loop Load

The Coalesce node Looped Load dynamically groups incoming source data, incrementally if configured, and loads into target data by looping through those groups. It creates “load buckets” dynamically based on a selection of table keys and then use those buckets to loop through source data and load into a target.

Looped Load Node Configuration

The Looped Load node type has two configuration groups:

• Node Properties
• Options

Go to the node and select the config tab to see the Node Properties and Options.

Looped Load Node Properties

There are four configs within the Node Properties group.

• Storage Location: Storage Location where the WORK will be created.
• Node Type: Name of template used to create node objects.
• Description: A description of the node's purpose.
• Deploy Enabled:
• If TRUE the node will be deployed / redeployed when changes are detected.
• If FALSE the node will not be deployed or will be dropped during redeployment.

Looped Load Options

• Enable tests: This toggle can be enabled to perform some data quality tests.
• Pre-SQL: Any SQL to be executed as a predecessor to data insert operation can be mentioned here.
• Post-SQL: Any SQL to be executed post the data insert operation can be specified here.

Looped Load Load Options

• Load Type:This toggle helps you to choose different accepted Load Types from Config.If no load type pararmeter is specified in the workspace,then it falls back to the config level load type.

Looped Load Record Selection Options

• Grouping Type:
• Key Based: The incoming source data is grouped based on the bucket column as the key.
• Range Buckets: The incoming source data is grouped based on the bucket column into different groups mentioned in 'Number of Buckets' textbox.
• Number of Buckets: The number of groups based on which data will be divided.
• Bucket Columns: Add bucket columns.
• Sort Group Data on Load: True/False toggle that determines whether to add GROUP BY ALL to SQL Query.
• Sort Colums: The Column name and sort order are prompted.

Looped Load Incremental Load Options

• Set Incremental Load Options:
• True: Prompts for load column based on which incremental data is loaded
• False: Incremental processing is not done
• Incremental Load Column(date): A date column based on which incremental data is loaded
• Group Incremental: True/False toggle that determines whether to group data into single group or groups specified in the 'number of buckets' textbox.
• True: The data is grouped on the number of buckets inputed
• False: The data is grouped into a single group

Looped Load Group Table Options

• Dedicated Load History Table:

• True: A history table specific to this target table is created by prefixing target table name to TABLE_GROUP_LOAD.

• False: A history table with common name TABLE_GROUP_LOAD is created.
• Load History Table Location:
• Same as Target: The history table is created in the same location as Target table.
• Utility Schema: The history table is created in the location specified in UtilitySchema parameter.

Looped Load Parameters

The Looped Load node specifies a loadType parameter to perform:

• A full load
• A full reload
• Incremental load
• Reprocess load

Also a parameter utilitySchema can be used to set a target table in a location other than target table location.

json { "loadType_accepted_values": [ "Incremental Load", "Full Load", "Reprocess Load", "Full Reload" ], "loadType": "Full Load", "utilitySchema": "TARGET_DB" }

Key Points on Looped Load Node

• No data gets loaded when Load_type is set to Reprocess load if the previous run was all successful. Only when the previous runs has any entries with process status '-1' denoting failure, data gets loaded during Reprocess Load.
• The choice of bucket column is crucial for Keybased grouping as choosing a column with distinct unique values affects the performance of data load.

Looped Load Deployment

Looped Load Initial Deployment

When deployed for the first time into an environment the Looped load node will execute the following stages:

• Create Load Group Table: This will execute a CREATE OR REPLACE statement and create a load group table in the target environment.
• Create Stage Table: This will execute a CREATE OR REPLACE statement and create a table in the target environment.

Looped Load Redeployment

After the Looped Load has been deployed for the first time into a target environment, subsequent deployments with column level changes or table level changes may result in altering the target Table.

Looped Load Altering the Target Tables

There are few column or table changes like Change in table name,Dropping existing column, Alter Column data type,Adding a new column if made in isolation or all-together will result in an ALTER statement to modify the Work Table in the target environment.

The following stages are executed:

• Clone Table: Creates an internal table
• Rename Table | Alter Column| Delete Column | Add Column | Edit table description| : Alter table statement is executed to perform the alter operation accordingly;
• Swap cloned Table: Upon successful completion of all updates, the clone replaces the main table ensuring that no data is lost.
• Delete Table: Drops the internal table

Looped Load Undeployment

If a Incremental load node of materialization type table is deleted from a Workspace, that Workspace is committed to Git and that commit deployed to a higher level environment then the stage table in the target environment will be dropped.

This is executed in two stages:

• Delete Table: Coalesce Internal table is dropped.
• Delete Table: Target table in Snowflake is dropped.

If a Incremental load node of materialization type view is deleted from a Workspace, that Workspace is committed to Git and that commit deployed to a higher level environment then the StageView in the target environment will be dropped.

The stage executed:

• Delete View: Drops the existing stage view from target environment.

Run View

The Coalesce node Run View is a variant of basic View node type.In contrast to standard View node,the custom node Run View actually includes the view created logic in the Run tab. When a job using these views executes the view will be recreated as part of the job and will utilize whatever parameter values are passed in. The parameters are used for selecting which sources to load into the target table.

Run View Node Configuration

The Run View node type has two configuration groups:

• Node Properties

• Options

Go to the node and select the config tab to see the Node Properties and Options.

Run View Node Properties

There are four configs within the Node Properties group.

• Storage Location: Storage Location where the WORK will be created.
• Node Type: Name of template used to create node objects.
• Description: A description of the node's purpose.
• Deploy Enabled:
• If TRUE the node will be deployed / redeployed when changes are detected.
• If FALSE the node will not be deployed or will be dropped during redeployment.

Run View Options

• Multi Source: True / False toggle that is Coalesce implementation of SQL UNIONs.
• True - Multiple sources can be combined in a single node. The sources are combined using the option specified in the Multi Source Strategy.
• False - Single source node or multiple sources combined using a join.
• Override Create SQL:True/False that determines whether a customized Create SQL is required to be executed.
• True - Customized Create SQL specified in the Create SQL space is executed.All other options are invisible.
• False - Create view SQL based on the options chosen are framed and executed.
• Filter data based on source:True/False that determines whether data is to be filtered based on parameter
• True - Length of source suffix is required to be added to frame the filter in join clause.A point to remember here is clear the join tab and use the 'Copy To Editor' to add the new join after enabling 'Filter data based on source' option
• False - No filter is added to the join tab.

Run View Increment Options

• Incremental load based on Persistent table: True / False toggle that helps us to load incremental load.
• True - provides option to perform incremnetal load.
• False - a normal initial load of data from source is done.
• Persistent table location (required): The Coalesce storage location is required to be added here.
• Persistent table name (required): The table name of the persistent table is required to be added.
• Incremental load column(date): A date column based on which incremental data is loaded.

Run View Example Workflow

1. Add a source node.
2. Add the Run View nodes on different sources.
3. Leave the Filter data based on Source option set too false.
4. Create the base views from source.
5. Add another view node with multi source enabled to combine the sources created.
6. Enable the multi-source toggle and Filter data based on Source.
7. Enter the length of the source suffix to identify the source.For instance if the source names follow the pattern RV_CUSTOMERA,RV_CUSTOMERB ,then the length of suffix can be set to 1 or if the source names follow thw pattern RV_COURSES_IT,RV_COURSES_SC,then the length of suffix can be set to 2 to uniquely identify the source to be loaded.
8. Ensure the sourcesuffix for sources follow unique pattern like an alphabetical sequence(A,B,C,D) ,numerical sequence(1,2,34) or any meaningful pattern('SC','IT').
9. Set the parameter sourcesuffix toALL if you want to process all sources else set in accordance with the preferred sources to be processed/
10. Remove the existing (basic) join and use the 'Copy To Editor' to add the new join, including the filter clause for filtering out data from specific sources.
11. Create and Run the Run View.
12. You can dynamically create a view with data from preferred sources in case of multiple sources.

Run View Incremental Processing Example

1. Add the Persistent table to the view.
2. Create and Run the node.
3. Now go back to the Run View node and set the Incremental options in Config.
4. Remove the existing (basic) join and use the 'Copy To Editor' to add the new join, including sub-select.
5. Re-run the Run View node.

Tips on Choosing the Source Suffix

• Ensure that the multiple sources have the source name suffixes with a uniform pattern and length.
• For example,the multiple sources can be named PRODUCTA, PRODUCTB, PRODUCTC, and so on. In which case we can set the parameter sourcesuffix to ('A') to process only source PRODUCTA, ('A','B') to process sources PRODUCTA,PRODUCTB and ('ALL') to load all sources.In similar way we can have numerical suffixes as well. In this case the source suffix length in Config is to be set to 1.
• Another example, source suffixes can have a meaningful pattern with uniform length like PRODUCT_ELEC, PRODUCT_HOME, PRODUCT_SPTS wherein the parameter sourcesuffix can be ('ELEC'),('HOME'),('ALL'). In this case the source suffix length in Config is to be set to 4

Run View Parameters

The Run View node specifies a sourcesuffix parameter for selecting which sources to load into the target table.The sourcesuffix refers to the suffix of the sources you want to load to the target view.

For instance,if we have multiple sources like RV_CUSTOMERA, RV_CUSTOMERB, and RV_CUSTOMERC.

• You can set the sourcesuffix to 'A' if you want to add data from only source RV_CUSTOMERA to target data.

json { "sourcesuffix": "('A')" }

• You can set the sourcesuffix to 'A','B' if you want to add data from only source RV_CUSTOMERA and RV_CUSTOMERB to target data.

json { "sourcesuffix": "('A','B')" }

• You can set the sourcesuffix to 'ALL' if you want to add data from all sources to target data.

json { "sourcesuffix": "('ALL')" }

• You can add numeric prefixes.

  json { "sourcesuffix": "('1','2')" }

Run View Deployment

When deploying the DAG using Run View nodes the environment parameter should be set to DEPLOY.

Deployment Value - When deploying this pipeline, use this parameter value.

json { "sourcesuffix": "('DEPLOY')" }

When running a job with this pipeline, fill in the parameter with the sources you want to execute.

Run View Initial Deployment

When deployed for the first time into an environment the Run View will execute the following stages:

• Create View: This will execute a CREATE OR REPLACE statement and create a view in the target environment.

Run View Redeployment

The subsequent deployment of View node with changes in view definition,adding table description,adding secure option or renaming view results in recreating the view.

Run View Recreating the View

The following stages are executed:

• Create View

Run View Undeployment

If a View Node is deleted from a Workspace, that Workspace is committed to Git and that commit deployed to a higher level environment then the View in the target environment will be dropped.

This is executed in the below stage:

• Delete View

Incremental Load Code

• Node definition
• Create Template
• Run Template

Looped Load Code

• Node definition
• Create Template
• Run Template

Run View Code

• Node definition
• Create Template
• Run Template

Run View Macros

• Macros

Comments added in Insert clause of Incremental load removed

Initial Versions