Collibra Platform Announcements — release 2026.09 (4 Sep 2026) and carried 2026.08 items

Tag: S-2026-09-04-collibra-202609-announcements Type: report (primary product documentation — Collibra Product Resource Center “Announcements” page) Author(s): Collibra Date of source: 2026-09-04 (page header; 2026.09 items dated 4 Sep 2026; 2026.08 items announced with the 21 Aug 2026 release) Date ingested: 2026-09-08 Authority weight: high for the lifecycle facts (primary vendor documentation, dated per release, action-required sections); note it is silent on rationale for most changes Raw file: S-2026-09-04-collibra-202609-announcements.md

What it claims

The Announcements page, current to the 2026.09 release of 4 September 2026, records the following new or recently added platform lifecycle notices:

• Collibra Units vector-storage price decrease (2026.09, 4 Sep 2026). Vector storage costs for Collibra AI are lowered, applied automatically, effective 3 Sep 2026 in CU balances, with a retroactive adjustment credit for early adopters.
• Google Dataplex ingestion frozen (2026.09). Dataplex ingestion “is no longer in active development and will only update for defect fixes”; documentation is removed from 2026.09 (retained in the 2026.08 doc set); the Google Knowledge Catalog integration via Edge is recommended as the maintained path for GCP metadata.
• End of Life for log access through Collibra Console (2026.08). Log access has moved to Collibra Settings; the Console API log endpoints (dgcLog) and the Console-based Log Proxy reach End of Life “later this year”, to be replaced by a forthcoming Collibra Log API and Log Proxy 1.4.0; customers with scripts/automation retrieving logs via Console must migrate “before 2027”. Access requires a global role with Logs > View permission.
• Derived relation types (preview) filter API rework (2026.08). REST/GraphQL filter structures renamed and made consistent; new string operators; stored definitions migrate automatically; but CMA package migration across the 2026.08 boundary fails in both directions.

The page also carries earlier notices already reflected in the vault: CLI lineage harvester and single-file custom lineage EoL (31 Jul 2026); external-mappings lastSyncDate behaviour change (default flips in 2026.10) and /mappings property deprecations; Import API continueOnError default change; PostgreSQL 14 support ending 12 Nov 2026; Jobserver EoL for Platform for Government (30 May 2027) and removal from commercial environments in September 2026.

Notable quotes

“The Google Dataplex ingestion is no longer in active development and will only update for defect fixes. We recommend the Google Knowledge Catalog integration via Edge as the actively maintained path for integrating GCP metadata.” (Dataplex section)

“The Console API log-related endpoints and the Console-based Log Proxy integration reach their End of Life later this year. If you use custom automation, scripts, or Log Proxy to retrieve logs through Collibra Console, migrate to the equivalent capabilities in Collibra before 2027 to avoid disruption.” (Console log EoL section)

“Migrating a CMA package from Collibra 2026.08 or newer that contains derived relation types with filters to a Collibra version older than 2026.08 will fail.” (Derived relation types section)

What’s speculative vs. asserted

• Asserted: every item above is a dated vendor statement of product status with explicit action-required steps.
• Unstated by source: rationale for freezing Dataplex ingestion (beyond recommending Edge); the exact EoL date for Console log endpoints (“later this year”); whether the Collibra Log API is available yet; the content of the 2026.09 feature release itself (release-notes page did not render — gap).
• Comparison line (not from source): the pattern of Edge-as-successor (lineage harvester → Edge in July; Dataplex → Edge-based Knowledge Catalog integration now) continues the platform-consolidation trend recorded on Collibra.

Topics this feeds

• Collibra — Tracked-changes entries (21 Aug and 4 Sep 2026), a lifecycle/integration-continuity bullet, and Open Questions on log-evidence continuity.

Open questions raised

• For FIs relying on Collibra audit/application logs as DORA or operational-resilience evidence, is there any retrieval gap between Console log EoL and Log API availability? Not stated.
• How many GCP-centric estates depend on Dataplex ingestion for BCBS 239 lineage or GDPR inventory coverage, and is the Edge path feature-equivalent? Not stated.
• What did the 2026.09 feature release actually add? Requires a successful fetch of the release-notes page in a future scan.