Release Notes 26.0.650.patch1

1. RELEASE INFO

2. CONTENT OF THE RELEASE

2.1 Highlights (in 26.0.650)

• New External API endpoints of entity import/export in YAML format for improved support of agentic AI workflows, in Private Preview (for selected customers)

• Workflow Orchestration: Apache Airflow 3 upgrade in Private Preview (for selected customers)

• New feature Review Request in Private Preview (for selected customers)

• New STORAGE.CHANGE_TRACKING support in Databricks SQL

• New API_CALL support for Databricks API endpoints

2.2 Fixes (in this 26.0.650.patch1)

• Third party security fixes

• Infrastructure robustness improvements

• Load options should also be limited by load type in backend

• External API gives 500 error when changing load type from LOAD_FILE to TRANSFORM_PERSIST with steps/opts

• Mapping import accepting any combination of physical type and load type

• Databricks SQL materialized view needs also changedatafeed and rowtracking properties for the refresh mechanism to function properly

3. NOTIFICATIONS

3.1 When the tenant has Apache Airflow 3 upgraded

When the tenant has Apache Airflow 3 upgraded for Workflow Orchestration, it starts from the clean state with its database (recommended by the open source project). The past executions and logs for Apache Airflow 2 can be accessed around 30 days by modifying the web browser URL from /dagger to /archiveddagger. The so-called archived Dagger ie. Airflow 2 is in read-only mode.

The main UIs of Apache Airflow 3