/
App Settings

App Settings

You can define the two types of settings in following tabs: Settings and Preview features. Settings are always set for the currently selected schema. Preview features are defined for the entire application and are used to enable or disable newly added features.

Preview Settings

These settings enable features that are currently have the status Preview.

  • [Preview] Update entire line during soft delete

    • When enabled, it can be turned off for a specific schema using the #Merge-settings → [Preview] Update entire line during soft delete setting.

  • [Preview] Cluster table delete

    • Removes rows from the merge table that were deleted from the cluster table. This is a mandatory setting when cluster tables are replicated. Can be disabled for specific schemas using the #Merge-settings → [Preview] Delete after merge for cluster tables setting.

  • [Preview] Prevent stream staleness

    • When enabled, it can be turned off for a specific schema using the #Source-settings → [Preview] Prevent stream staleness setting.

  • [Preview setting] Additional insert and update timestamp [Preview setting] Additional insert and Update timestamp

Settings

You can see the name schema which is currently selected at the top of the settings tab. If the schema does not match the one you have selected, click Refresh.

image-20250228-103503.png

Source Settings

  • Controller task scheduling period:

    • Defines how often the controller task runs.

    • This task triggers the delta merge check.

  • Backup retention period:

    • Defines the retention period for backups created after the table deactivation (in days).

  • Clean up staging tables:

    • Enable or disables the cleanup of already merged data in the staging tables. This action is performed once a day during housekeeping.

  • Stage table data retention period:

    • Defines the retention period for already merged data in staging tables (in days). Minimum value: 30 days.

  • Backup retention period for statistics:

    • Defines the retention period for statistics (in days). The deletion is performed once a day during housekeeping.

  • [Preview] Prevent stream staleness:

    • If enabled housekeeping executes system function SYSTEM$STREAM_HAS_DATA on streams to prevent empty streams with paused tasks from becoming stale.

image-20250228-103426.png

Merge Settings

These settings are applied during the creation of the table in Snowflake. As a result, any changes, will not apply automatically, except for Delta-size based merge. You must execute the procedure DEPLOY_MERGE for changes to take effect. For more information, see the chapter API Merge .

  • Warehouse:

    • Defines the warehouse that is used for the merge execution.

  • Suffixes for merge objects: Defines a suffix.

    • The resulting name for the merge object is <Staging table name>+<suffix>.

    • You can define a suffix for the following objects:

      • Merge table

      • Merge view

      • Merge stream

      • Merge task

  • Use custom schema for merge objects:

    • Generates merge objects in their respective schema instead of the staging table schema.

    • The defined schema cannot exist as a source schema or be defined for another source schema.

    • You can define a schema for the following objects:

      • Merge table

      • Merge view

      • Merge stream

      • Merge task

  • Merge scheduling:

    • Standard:

      • Merge scheduling period: How often the merge task runs.

      • Time in: Hours or minutes

    • Scheduled:

      • Merge scheduling period: How often merge task runs.

      • Time in: Hours only

      • Merge scheduling step: Time in minutes between the execution of the individual merge tasks.

  • Delete type

    1. Soft: Stores deleted entries in the merge table with a deletion flag.

    2. Hard: Does not store deleted entries in the merge table.

  • Display soft deletes in merge view:

    • Displays entries with a delete flag in the merge view.

  • Delta-size based merge:

    • Uses the stream row count as the trigger for the merge.

  • Delta size to trigger merge:

    • Defines the stream row count needed to trigger the merge.

  • [Preview] Delete after merge for cluster tables:

    • Removes rows from the merge table that were deleted from the cluster table. This is a mandatory setting when cluster tables are replicated.

  • [Preview] Update entire line during soft delete:

    • If enabled, the entire row is updated during the soft delete.

    • If disabled, only key fields and timestamp field are updated.

Metadata Settings

These settings are applied during the creation of the table in Snowflake. As a result, any changes, will not apply automatically, except for Delta-size based merge. You must execute the procedure DEPLOY_MERGE for changes to take effect. For more information, see the chapter API Merge .

  • Timestamp field:

    • Defines the name of the field used to determine the last record of a specific key.

  • Change field:

    • Defines the name of the field used to determine the CDC action.

  • Insert flag:

    • Defines the identifier in the metadata that represent inserts. You can insert multiple values if they are separated by a comma. Use the <empty> placeholder for a space.

  • Update flag:

    • Defines the identifier in the metadata that represents updates. You can insert multiple values if they are separated by a comma. Use the <empty> placeholder for a space.

  • Delete flag:

    • Defines the identifier in the metadata that represent deletes. You can insert multiple values if they are separated by a comma.

image-20250228-103617.png