warning

This page is intentionally hidden from navigation but remains accessible via direct link. It is retained for internal reference purposes only and may contain outdated or transitional content.

Analysis Server Custom Transformation

This document describes the transforms asset group for the Dagster-based Analysis Server orchestration.

Overview

The transforms group is automatically materialized after the coredatabase group. It is equivalent to running the AnalysisServer ProcessSql job.

Configuration Location

Transform asset definitions are stored by default in C:\Program Files\OpeniT\Analysis Server\Configuration\dagster\defs\process_sql.

Use these files as follows:

• defs.yaml contains the default transform asset definitions.
• custom_defs.yaml is for customer-specific transform assets. Keep the default definitions in defs.yaml and place custom additions in custom_defs.yaml.

Adding a Custom Asset

To add a custom asset or stored procedure, update custom_defs.yaml.

Use an entry like this:

Example

-   name: asset_name
    sub_command: RunProcedure
    argument: storedprocedurename
    dependencies:
        - names: ["the_upstream_asset_name"]

Field Definitions

• name is the Dagster asset name and should use snake_case.
• sub_command is the operation to run.
• argument is the stored procedure name or command argument.
• dependencies defines optional upstream asset dependencies.

note

Dependencies are optional, but they should be added when a custom transform must wait for another asset to finish first.

Example

dependencies:
    - names: ["the_upstream_asset_name"]

Limitation

Asset overrides are not supported yet.

You can add new custom assets through custom_defs.yaml, but you cannot replace existing default assets from defs.yaml.

Applying Changes

After updating custom_defs.yaml, restart the Open iT Dagster Analysis Server service so the new transform asset definitions are loaded.

Quick Checklist

1. Identify the stored procedure or command to add.
2. Add a new entry in custom_defs.yaml.
3. Use a unique snake_case name for the asset.
4. Add dependencies if the asset must run after another asset.
5. Restart the Open iT Dagster Analysis Server service.