Breadcrumbs

Release Notes 25.1

1. RELEASE INFO

Product

AGILE DATA ENGINE

Release

25.1.631

Release date

13th of April 2025

Release status

RELEASED

Release type

MAJOR.MINOR.UPDATE.PATCH

2. CONTENT OF THE RELEASE

2.1 New features

Advanced SQL Templating

Metadata Interface Additions

Database Features

  • Snowflake key pair authentication supported in Private Preview (full availability by end of June 2025)

  • Support of referencing database names in grantee configuration to achieve e.g. in Snowflake: GRANT SELECT on <otherdb>.schema.table TO ROLE <otherdb>.SELECT_ROLE, which enables also the use of Snowflake DATABASE ROLEs

Workflow Orchestration

  • New time zone setting for Load Schedules / Workflows / DAGs based on Airflow feature of time zone aware DAGs

  • New priority weight setting for Load Schedules / Workflows DAGs based on Airflow feature of setting priority weights

  • New variable entity_lock_timeout_in_secs to support setting entity lock timeout time together with new load option OPT_LOCK_TIMEOUT_IN_SECS on environment, workflow & load levels

2.2 Improvements

  • Update of Apache Airflow version

  • Add database connection / transaction / query IDs to be shown in Deployments UIs and in Workflow orchestration logs

2.3 Fixes

  • Designer’s entity import from a source file hangs when analyzing file and reanalyzing then gz file without closing analyzer in-between

  • Current view entities are not updated when technical attribute type is changed in the underlying entity

  • Satellites' reference keys are named differently than current satellites' reference keys

  • Fixed attribute default value handling in Config Entity Defaults

  • Config Datatypes user interface requires uniqueness over physical data type + dbms product

  • Fixed internal datatype comparison during deployment when attribute data type length setting was left empty

  • Views created in Google BigQuery do not add column comments properly

  • NOT NULL column addition fails to an existing Google BigQuery table

  • When using variable reference of <target_entity_attribute_list_with_transform> in S_MA (multi-active satellite) it is not resolved