Control / params · All operations

Read run and system information

A variant of Set parameters

Read built-in values about the current run or machine, such as the run date, processing window, user or version.

Status

In arcform

Not built yet

arcform does not do this yet; it would live in how a Protocol runs. Its place on the roadmap

What other tools call it

Meridian's classification; an independent blind rating agreed on 95.7% of 324 rows (variant, version 3).

Apache Hop (1)
  • Get System Inforead 2026-09-27

    Add system values such as dates, host name, pipeline name and run ids as fields

Bruin (2)
  • Built-in Variablesread 2026-09-27

    Run-window and run-context values injected into the Jinja context, such as start_date

  • Interval Modifiersread 2026-09-27

    Shift the start or end of the processing window to catch late or early data

DuckDB (4)
  • Utility Functions (family)read 2026-09-27

    The functions documented on the Utility Functions page

  • pragma_platformread 2026-09-27

    pragma_platform table function

  • pragma_user_agentread 2026-09-27

    pragma_user_agent table function

  • pragma_versionread 2026-09-27

    pragma_version table function

EasyMorph (1)
  • System informationread 2026-09-27

    Emit one row of runtime facts: Windows account, free RAM, machine name, UTC offset, run ID

KNIME Analytics Platform (2)
Pentaho Data Integration (1)
  • Get System Inforead 2026-09-27

    Add system values such as the system date and arguments as fields

SQLMesh (6)
  • @RESOLVE_TEMPLATEread 2026-09-27

    Render a template from the catalog, schema and table parts of the physical table name

  • @gatewayread 2026-09-27

    Name of the current gateway

  • @model_kind_nameread 2026-09-27

    Name of the current model kind, for model defaults

  • @runtime_stageread 2026-09-27

    Current runtime stage: loading, creating, evaluating, promoting, demoting, auditing, testing

  • @this_modelread 2026-09-27

    Physical table name the model view selects from; used in generic audits

  • Temporal variables (family)read 2026-09-27

    27 variables: start, end, execution x dt, dtntz, date, ds, ts, tstz, hour, epoch, millis

Background

Apache Hop's Get System Info transform retrieves information from the Hop project, or the environment or system Hop runs on, as a single row.[1] Bruin automatically gives templated assets built-in variables, such as a run's start and end dates, the pipeline's name and a unique run identifier.[2] In DuckDB, utility functions such as version() and current_database() return the active DuckDB version and the active database's name.[3]

When to use it

In Apache Hop, the System date (variable) value changes every time it is asked for, while System date (fixed) is determined at the start of the pipeline.[1] Stamp a run with one fixed time taken at its start, so every row it writes agrees on when it happened. (Meridian's view) In Bruin, a SQL asset can filter its rows to those between the run's start date and end date with the start_date and end_date variables.[2] Filter on the run's own start and end dates rather than on today's date, so re-running a past day reprocesses that day and not the current one. (Meridian's view)

EasyMorph's System information action can be used to check that a system has enough available memory before running a known memory-intensive workflow.[4] In EasyMorph, the workflow run ID is the same for every module or project called during one workflow run, and changes for each new run.[4] In DuckDB, getenv returns the value of a named environment variable, and is available only in the command line client.[3] Check that a value you rely on exists in every client the pipeline will run in, not only the one it was written in. (Meridian's view)

The method

Apache Hop's Get System Info transform lets each output field be given a name and a type of system information to retrieve.[1] The system information types in Apache Hop's Get System Info include the pipeline name, the hostname and the current process identifier (PID).[1] EasyMorph's System information action generates a single-row dataset of items such as the Windows account name, free memory, the machine name, the offset from Coordinated Universal Time (UTC) and the workflow run ID.[4]

Bruin's built-in variables include commit_hash, the current git commit of the pipeline's repository, and full_refresh, which says whether the run is a full refresh.[2] In Bruin, built-in variables are exposed to Python assets as environment variables with a BRUIN_ prefix.[2] Record the engine version and the code commit a run used beside its output, so a changed result can be traced to a changed engine or changed code. (Meridian's view)

Sources

  1. [1]Get System Info | Apache Hopdocumentation
  2. [2]Built-in Variables | Bruin CLIdocumentation
  3. [3]Utility Functions – DuckDBdocumentation
  4. [4]SYSTEM INFORMATION [EasyMorph Help]documentation