Release Notes 26.0.649

1. RELEASE INFO

2. CONTENT OF THE RELEASE

2.1 Highlights

• Support of CREATE OR REPLACE syntax (instead of DROP & CREATE pattern) for TABLEs, VIEWs, and MATERIALIZED VIEWs in entity re-create cases where possible in Google BigQuery. See 3.1 Notifications for exceptions

• Important infrastructure third party software updates

2.2 New Features

• New objects added to the Metadata Interface: ENTITY_TYPE, TECHNICAL_ATTRIBUTE_TYPE, ATTRIBUTE_TRANSFORMATION_TYPE

• New <generated_transformation_query> and <transformation_query> variables to be used in custom SQL load steps and load options

• Dependencies between two packages which are configured into two different target instances made possible in Deployment Management and Workflow Orchestration with a separate feature flag – ask for more details

• New physical option: STORAGE.ICEBERG_POINTER_FILE_NAME

2.3 Other

• VIEW definition clauses are migrated from OVERRIDE to TRANSFORM load step type in metadata

• Fixed: Database tags are not copied to/from Current Views with Map & Add

• Fixed: metadata_interface.ENTITY_VERSION orderBy fails

• Fixed: exec_time_ms_avg serialization error in WORKFLOW_STATS_WEEK of Metadata Interface endpoint

• Fixed: API_CALL should handle also TransportError

• Fixed: Changing a reference in Designer might have caused incoherent state in metadata if referenced entity is changed

3. NOTIFICATIONS

3.1 Note that DROP & CREATE pattern is still required in certain cases in Google BigQuery

• In case of a VIEW or MATERIALIZED VIEW when any of these have changed:

  • project / schema (dataset) name

  • view name

• In case of a TABLE when any of these have changed:

  • clustering

  • partitioning

  • project / schema (dataset) name

  • table name in case of a primary key is defined for the table