Release 2025.02
Release versions and dates
Name | Description | Availability |
---|---|---|
Collibra platform |
Collibra Cloud for Government 2025.02.3 |
February 24, 2025 |
Collibra 2025.02.3 | February 23, 2025 (production environments) | |
Collibra 2025.02.3 | February 21, 2025 (on demand only) | |
Collibra 2025.02.2 | February 14, 2025 (on demand only) | |
Collibra 2025.02.1 | February 07, 2025 (on demand only) | |
Collibra 2025.02.0 | February 02, 2025 (pre-production environments) | |
Documentation Center | January 30, 2025 | |
Release notes | January 20, 2025 | |
Edge | Edge 2025.02.56 | March 30, 2025 |
Edge 2025.02.49 | March 23, 2025 | |
Edge 2025.02.35 | March 9, 2025 | |
Edge 2025.02.28 | March 2, 2025 | |
Edge 2025.02.20 | February 22, 2025 | |
Edge 2025.02.7 | February 09, 2025 | |
Data Lineage | Data Lineage 2025.03.6 | March 31, 2025 |
Data Lineage 2025.03.5 | March 25, 2025 | |
Data Lineage 2025.03.4 | March 24, 2025 | |
Data Lineage 2025.03.3 | March 17, 2025 | |
Data Lineage 2025.03.2 | March 10, 2025 | |
Data Lineage 2025.03.1 | March 3, 2025 | |
Data Lineage 2025.02.4 | February 24, 2025 | |
Data Lineage 2025.02.3 | February 17, 2025 | |
Data Lineage 2025.02.2.1 | February 11, 2025 | |
Data Lineage 2025.02.2 | February 10, 2025 |
Ticket | Product | Area | Type | Content | UI | Beta | Not CPSH | Not GovCloud | Related topic | Idea |
---|---|---|---|---|---|---|---|---|---|---|
DEV-116923 | Administrative | Workflows | Fixed | Scrolling on a "Tasks" page with more than 50 rows no longer causes a jump to the first row. | latest | |||||
DEV-115167 | Administrative | New and improved | You can now add an asset type to an asset type group from the "Overview" tab of an asset type group page. | Asset type groups | ||||||
DEV-114547 | Administrative | General settings | Fixed | The "Relation types" table no longer contains the relation types of complex relations. | ||||||
DEV-113811 | Administrative | Import and export | Fixed | The export progress dialog box no longer stops at 99% even if the export is ready. | latest | |||||
DEV-112294 | Administrative | Fixed | You no longer see the "Configuration" system-managed global permissions. | |||||||
DEV-110449 | Administrative | General settings | New and improved | The "Manage OAuth" feature is now generally available. You can register your applications to obtain a client ID and client secret required to request an access token. This allows you to securely authenticate your applications to access Collibra public APIs without using individual user credentials. | true | OAuth Applications settings page | DGCPLAT-I-500 | |||
DEV-108177 | Administrative | Workflows | Fixed | Selecting one or more tasks to cancel in bulk no longer duplicates the "Cancel" button. | ||||||
DEV-106184 | Administrative | Workflows | Fixed | Leading or trailing spaces in user, group, or role names in a proposed values drop-down list no longer cause a workflow form to break. | ||||||
DEV-106083 | Administrative | Workflows | Fixed | When exceeding the maximum number of items for multiple selection fields, workflow forms now show your custom error message instead of the default one. | ||||||
DEV-101736 | Administrative | Users and subscriptions | Fixed | Deleting a user now also deletes their profile photo. | ||||||
DEV-96806 | Administrative | General settings | New and improved | The migration import logic now considers the public ID for most resources and generally performs matches on resource ID, public ID, and then the resource name. | Migration import logic | |||||
DEV-77154 | Administrative | Users and subscriptions | Fixed | Following a password reset link from a password reset email no longer leads to a blank page if you are currently signed in to Collibra. | latest | |||||
DEV-70568 | Administrative | Users and subscriptions | Fixed | Deleting a user now immediately removes the user from the "Users" table. | latest | |||||
DEV-41443 | Administrative | Collibra Console | New and improved | The date format in the "Backups" section of Collibra Console is now YYYY-MM-DD. | DCC-I-1430 | |||||
DEV-112462 | Administrative | Fixed | The "Name" column of the "Global Roles" table no longer maintains a minimum width. | latest | ||||||
DEV-114513 | AI Governance | Fixed | The “Other Policies That Apply” widget (beta) now shows Policy assets and assets of child asset types. Previously, only Policy assets were shown. | latest | Identifying indirectly related policies and data categories | |||||
DEV-115001 | API | Fixed | The "typeId" fields, previously deprecated in favor of "publicId" in earlier versions of REST and Java APIs, are no longer deprecated. | |||||||
DEV-113827 | API | Fixed | SCIM synchronization no longer causes out-of-memory issues in some cases. | |||||||
DEV-109564 | API | New and improved | You can now access the documentation for the following APIs in your environment:
|
|||||||
DEV-96806 | API | New and improved | The Collibra REST and Java Core APIs now support the "publicId" parameter for finding, creating, or updating most resources and resource types. | |||||||
DEV-27507 | API | Fixed | You can no longer retrieve the tags of assets for which you don't have view permissions using the /assets/{assetId}/tags endpoints of the REST Core API v2. | |||||||
DEV-115529 | Assessments | New and improved | You can now publish a template for a Data Attribute asset type with the "Copy Response to Assessed Asset" checkbox selected. | latest | ||||||
DEV-113781 | Assessments | New and improved | You can now print an assessment or download it as a PDF using the new "Print" button. The printed or PDF version also supports rich text responses. | latest | ||||||
DEV-110138 | Assessments | New and improved | You can now format field descriptions in a template. This allows you to highlight important information and include links to articles, such as the EU AI Act or other external documents for more context, helping users better understand the purpose and relevance of each question in the assessment. | latest | ||||||
DEV-108651 | Assessments | Fixed | If you first assign someone to an assessment with notifications enabled and then create the assessment, an email is now sent to the assignee. | latest | ||||||
DEV-121007 | Collibra maintenance updates | Collibra 2025.02.3 | Fixed | The Quality tab now correctly shows the data quality score when the head asset of the starting relation type in the aggregation path is a generic asset or when the starting relation type is based on the co-role instead of the role of the relation type. | ||||||
DEV-119998 | Collibra maintenance updates | Collibra 2025.02.2 | Fixed | We improved the Edge site upgrade process. | ||||||
DEV-119842 | Collibra maintenance updates | Collibra 2025.02.2 | Fixed | You no longer need to manually save your responses when conducting an assessment. Responses are now automatically saved, and all questions are always shown in edit mode. Changes in the "Properties" sidebar or assessment name are saved when you click outside the field. Additionally, a message appears below each response to show who last edited it and when. | latest | CAIG-I-81 | ||||
DEV-119842 | Collibra maintenance updates | Collibra 2025.02.2 | Fixed | Clicking "Conduct Assessment" on the Assessments landing page now creates an assessment in the "Draft" status. | latest | |||||
DEV-119770 | Collibra maintenance updates | Collibra 2025.02.1 | Fixed | We fixed an issue that caused the "An Error Occurred. Please contact your Collibra administrator" error message when a lineage synchronization is started. | latest | |||||
DEV-118954 | Collibra maintenance updates | Collibra 2025.02.1 | Fixed | Removing a characteristic from the Database asset type in the layout editor no longer causes an error. | latest | |||||
DEV-117832 | Collibra maintenance updates | Collibra 2025.02.2 | Fixed | JSON files included in REST API calls are parsed again as "application/json" instead of "text/plain". | ||||||
CFT-3429 | Data Catalog and Data Source Integrations | New and improved | The "Description" field on Catalog asset pages no longer includes the "Source Code" functionality. Use the "HTML Editor" option instead. | latest | Text editors | |||||
DEV-114531 | Data Catalog and Data Source Integrations | Fixed | The "Classification Results" report is now sorted alphabetically. | latest | ||||||
DEV-114459 | Data Catalog and Data Source Integrations | Fixed | You can now delete an S3 File System asset that was created for ingestion via Jobserver. | |||||||
DEV-113854 | Data Catalog and Data Source Integrations | Fixed | When you cancel a classification job from the "Activities" page, all outstanding related Edge jobs are now correctly canceled as well. | |||||||
DEV-112228 | Data Catalog and Data Source Integrations | New and improved | The "Integration Configuration" page for a capability now has more space for configuration fields, making it easier to use. To schedule a synchronization, click the synchronization icon instead of the "Add Schedule" button. |
latest | ||||||
DEV-112203 | Data Catalog and Data Source Integrations | Fixed | Your work now remains available when you open a dialog box while configuring an integration. | latest | ||||||
DEV-111992 | Data Catalog and Data Source Integrations | Fixed | You no longer receive an error if one or more descriptions are missing during a bulk description generation by Collibra AI. | latest | true | true | Create descriptions for columns in a table with Collibra AI | |||
DEV-111967 | Data Catalog and Data Source Integrations | New and improved | The MLFlow AI model asset type is now added to the operating model in preparation of the upcoming MLFlow AI model integration via Edge. | latest | true | |||||
DEV-111715 | Data Catalog and Data Source Integrations | Fixed | The "Descriptive statistics," "View Array," and "View Struct" links in asset views now open their respective dialog boxes on first click. | |||||||
DEV-111446 | Data Catalog and Data Source Integrations | Fixed | The "Classification Results" report now shows accurate data. | latest | ||||||
DEV-110144 | Data Catalog and Data Source Integrations | Fixed | Data source synchronization now completes even if a workflow triggered by the "Database Registration Completed" event fails. | |||||||
DEV-109707 | Data Catalog and Data Source Integrations | Fixed | JDBC data source synchronization on Edge no longer processes schemas with names that contain only whitespace. These schemas are also no longer visible in the list of "Available Schemas" on the "Configuration" tab of Database assets. | |||||||
DEV-109227 | Data Catalog and Data Source Integrations | Fixed | The Catalog Home page no longer shows Data Set asset recommendations if the "Catalog recommender enabled" setting is disabled. | latest | true | true | ||||
DEV-109184 | Data Catalog and Data Source Integrations | New and improved | You can now integrate SAP Datasphere, SAP Analytics Cloud, and SAP Business Glossary in a single integration, and synchronize all metadata via a single synchronization. As part of this unified integration, relations are now automatically created between SAC Story assets and SAP Datasphere Analytic Model assets.
Important To benefit from this unified integration, you need:
|
true | Steps overview: Integrate SAP Datasphere via Edge | |||||
DEV-103254, DEV-117799 | Data Catalog and Data Source Integrations | New and improved | The classification rules for most out-of-the-box data classes are now refined to improve accurate data classifications. Updates include changing regular expressions, maintaining the list of values, and adding rules based on data type. To benefit from the latest data class definition, reimport the required data classes. Note that reimporting replaces any fine-tuning done since the last import. Some examples of updated out-of-the-box data classes
Additionally, Time zone offset (regex) is renamed "Time zone offset," and the following out-of-the-box data classes are removed and can't be imported anymore:
|
About out-of-the-box data classes in the Unified Data Classification method | ||||||
DEV-95805 | Data Catalog and Data Source Integrations | New and improved | The AWS Bedrock AI integration via Edge is now generally available. This integration allows you to integrate metadata of ML models from Amazon Bedrock AI into Collibra. The resulting assets represent the AWS Bedrock AI models. | latest | true | About AWS Bedrock AI | ||||
DEV-85011 | Data Catalog and Data Source Integrations | New and improved | You can now classify dates and times based on the column type by defining a new data classification rule, "Data type." | About data classes in the Unified Data Classification method | ||||||
DEV-85011 | Data Catalog and Data Source Integrations | New and improved | Samples of dates and time are now shown correctly in the "Sample Data" section on Table and Column asset pages. | |||||||
DEV-95394 | Data Notebook | New and improved | Data Notebook now supports the Amazon Athena data source. | latest | beta | true | true | |||
DEV-95390 | Data Notebook | New and improved | You can now allow users to individually request access to the Data Notebook application, improving data use with personalized access while still maintaining strong governance. | latest | beta | true | true | Data Notebook, Request Data Notebook access (beta), Notebook settings | ||
DEV-66475 | Data Notebook | New and improved | Data Notebook is now available in all supported languages. | latest | true | true | ||||
DEV-105585 | Data Privacy | Fixed | The following out-of-the-box statuses now have descriptions: Feedback review, Ownership accepted, Ownership proposed, Ownership rejected, Review rejected, Waiting for feedback. Any custom descriptions you previously added are retained, keeping your work unaffected. | |||||||
DEV-114843 | Edge | Fixed | The Created Date for Edge images now shows the actual date the image was created. | latest | ||||||
DEV-114282 | Edge | New and improved | The Edge Tool is now deprecated with the 2025.02 release. If your Edge site doesn't have the Edge CLI, which was included in Edge site installers from the 2024.05 release, you must download it using the Edge CLI download command, and update your internal processes.
Note If you are not ready to use the Edge CLI, you must not upgrade to 2025.02 until your processes have been updated to use the Edge CLI. If you are on automatic upgrades, switch to Manual Upgrade mode to avoid auto-updating to 2025.02. |
|||||||
DEV-112434 | Edge | Fixed | You can now view and edit Edge connections linked to deleted vaults. Previously, when you deleted a vault that was added to a connection, an error appeared instead of an Edge site's Connections page. | latest | ||||||
DEV-111935 | Edge | Fixed | You no longer need to restart your Edge site when you update proxy settings via the Edge CLI or Helm chart. | |||||||
DEV-111652 | Edge | Fixed | We improved the security of the Edge Vault integration. Now, sensitive information pulled from a vault that is used in a connection is redacted from stacktrace logs. Fields that require you to manually enter sensitive information, for example, the Connection String, are shown in the logs, as expected. | latest | ||||||
DEV-111151 | Edge | Fixed | When you install an Edge site onto a bundled k3s cluster, the k3s SELinux download link now directs you to the correct location. | |||||||
DEV-108331 | Edge | New and improved | We improved our support for custom certificates on Edge sites. You can now:
|
|||||||
DEV-108326 | Edge | New and improved | You can now restart your Edge site from the Edge CLI if your Edge site is installed on a k3s or a managed Kubernetes cluster. | Edge CLI | ||||||
DEV-108253 | Edge | New and improved | When you create an Edge site capability, you can now filter for capability templates. | latest | CDC-I-12 | |||||
DEV-108197 | Edge | New and improved | We now support the following versions for our managed Kubernetes clusters:
|
Edge system requirements | ||||||
DEV-107188, DEV-113894 | Edge | New and improved | When you install an Edge site on a managed Kubernetes cluster, you can now configure User ID (UID) and Group ID (GID). This is available via both the Edge CLI and Helm Chart methods. If your Edge site is installed on an OpenShift Kubernetes cluster, you can also run your Edge site pods and containers with random UIDs. | |||||||
DEV-105203 | Edge | Fixed | When you uninstall an Edge site that was installed via the Helm chart method, the Edge site now successfully uninstalls regardless of the status of the Helm chart. | |||||||
DEV-104286 | Edge | Fixed | When you run a lineage capability on an Edge site installed via the Helm chart method with a forward proxy, the capability now runs successfully. Previously, lineage capabilities failed to run on these Edge sites. | |||||||
DEV-102576 | Edge | New and improved | You can now update certificates in your Edge site truststore without needing to reinstall your Edge site. This improvement makes it simpler to rotate your proxy or data source certificates and certificate authorities. | Edge CLI | ||||||
DEV-100132 | Edge | New and improved | We removed the setting NET_BIND_SERVICE as a requirement for OpenShift installations. If you have an existing Edge site installed on an OpenShift cluster, you need to update your current SCC settings to remove it. | Install an Edge site | ||||||
DEV-97719 | Edge | New and improved | We improved the Helm chart installation process, making it more straightforward and easy to use. For example, via the Helm chart method, you can now:
|
Install an Edge site | ||||||
DEV-97057 | Edge | Fixed | We removed an outdated component that caused some Edge sites to lose access to 1 CPU. | |||||||
DEV-96135 | Edge | Fixed | We fixed an issue where, in certain circumstances, the Edge site page couldn't load successfully. | latest | ||||||
General | New and improved | We're continuing the enhancement of the latest UI for consistency and stability. With 2025.02, you'll notice some visual changes to a number of components across the product to provide a more user-friendly and consistent experience. These changes don't impact functionality; all features and pages will continue to work just as they did before. Administrators will notice that the "Brand Chip" component has been removed from the "Custom Theme" page. For secondary buttons, the option to configure the light color has been removed, and changing the text color on hover has been replaced with changing it on click in the "Custom Theme" page. |
latest | Customize theme | ||||||
CFT-3429 | General | Text editor | New and improved | The standard text editor in the Comments field no longer includes the Source Code functionality. Instead, you can use the HTML Editor option. | Text editors | |||||
DEV-118751 | General | Asset management | New and improved | The new "Actions" menu is now shown on asset pages to provide a consistent location for accessing unpinned actions and workflows. This prevents accidental workflow triggers and ensures a cleaner, organized interface. The menu is hidden only when no actions are available. Additionally, administrators can now pin up to 5 actions to an asset layout, giving you quick access to important workflows. Pinned actions appear as buttons on the title bar, and buttons that don't fit in the title bar are grouped on the "Actions" menu. | latest | Asset page overview | IDEA-21, DGCPLAT-I-515, DIP-I-329, DIP-I-348, CDC-I-161 | |||
DEV-115815 | General | Asset management | Fixed | You can now add characteristic types via the asset layout editor to an asset type that is used in an asset type group. | latest | |||||
DEV-115712 | General | Asset management | Fixed | Threshold attributes with very small fractional values in tabular asset views on community and domain pages now show exact values instead of 0. | latest | |||||
DEV-114543 | General | Asset management | Fixed | You can now add columns to an asset view with a filter that includes an asset type group. | latest | |||||
DEV-114238 | General | Asset management | New and improved | The "At a glance" sidebar on asset pages is now hidden by default. For returning users, the sidebar remains visible if they last left it open and hidden otherwise. Note Clearing the cache always hides the sidebar. To show the sidebar, click the "At a glance" icon. |
latest | |||||
DEV-113863 | General | Asset management | Fixed | In an asset view with hierarchy enabled, the "Wrap text" icon now properly wraps the text in the "Name" column. | latest | |||||
DEV-113664, DEV-116564, DEV-115501 | General | Asset management | Fixed | We reduced the loading time of community pages, domain pages, and relations on asset pages. | latest | |||||
DEV-113623 | General | Asset management | Fixed | A role column showing inherited responsibilities in an asset view now allows you to filter based on an inherited responsibility. | latest | |||||
DEV-113132 | General | Asset management | New and improved | The behavior of cells in asset views on community and domain pages now matches global views. Edit mode is always enabled for cells, and a notification appears if you don't have permission to edit a cell. | latest | |||||
DEV-113068 | General | Asset management | Fixed | Anchor links on resource pages now take you to the intended section. Additionally, editing in the HTML editor no longer removes the IDs referenced in the anchor links. | latest | |||||
DEV-112766 | General | Asset management | Fixed | In an asset view with hierarchy enabled, you can now edit nested rows regardless of the number of rows shown per page. | latest | |||||
DEV-110911 | General | Dashboards | New and improved | The ability to add filters to a search widget and configure how result information is presented on the dashboard is now generally available. | latest | Search widget | ||||
DEV-102713 | General | Dashboards | New and improved | Dashboard ordering and the dashboard navigation panel are now generally available. You can order dashboards and edit multiple dashboards using the "Manage Dashboards" page in the dashboard navigation panel. | latest | Order dashboards | ||||
DEV-102688 | General | New and improved | The new navigation menu is now generally available in all Collibra environments. |
latest | ||||||
DEV-100124 | General | Asset management | New and improved |
A new commenting experience on asset, domain, and community pages is available if the "New Commenting Experience" setting in Collibra Console is enabled. It allows you to:
|
latest | New commenting experience | ||||
DEV-114406 | Protect | Fixed | If you create a rule with assets from multiple data sources but with groups mapped to only one data source, columns from the other data sources are now ignored. | latest | ||||||
DEV-115822 | Search | Fixed | We temporarily paused the semantic search (beta) feature introduced in version 2024.11. Semantic search was designed to provide results based on the intent behind your search text, even if specific keywords weren't present. If you had previously enabled this feature, it is now automatically disabled. This decision allows us to direct our efforts towards enhancing keyword-based search and performance to better meet your needs. | |||||||
DEV-115308 | Search | Fixed | Text in a search result is again selectable. | latest | ||||||
DEV-115007 | Search | Fixed | When setting the Data Marketplace scope, filtering asset types and statuses by name or description is now consistent with other filtering mechanisms in Settings. This change ensures a more intuitive and uniform user experience. | latest | ||||||
DEV-113642 | Search | New and improved | You can now add "Data Marketplace" and other search tabs as filters in the Search widget if you have the "Data Marketplace" global permission. When users search using a search tab in the widget, they are taken to the same tab on the search page. Searching using any other tab takes them to the "All Results" tab. | latest | Search widget | |||||
DEV-112765 | Search | Fixed | When you visit an Issue Type asset, it now appears in the drop-down suggestions as a recently visited asset. | |||||||
DEV-98524 | Workflow Designer | New and improved | You can now use OAuth to authenticate the API calls of the HTTP task component. | true | HTTP task | DCC-I-2035 |
Edge and Data Lineage updates 
These updates contain security and bug fixes for Data Lineage, Edge sites and their capabilities. These releases may be planned outside the regular monthly or quarterly release. You'll see the fix versions if you are manually upgrading an Edge site or reviewing logs.
March 31, 2025 (data-lineage-2025.03.5)
Collibra Data Lineage Service
- When ingesting any of the supported JDBC data sources, Collibra Data Lineage now provides improved analysis of SQL statements when a required database model is not available.
- When ingesting SQL Server Integration Services (SSIS) data sources, Collibra Data Lineage now
- Supports SSIS connections referenced by connection name.
- Handles incorrect connection strings gracefully.
- When ingesting DataStage data sources, Collibra Data Lineage now provides a suggestion for the Jobs property in the source configuration file when not provided.
- When ingesting Azure Data Factory data sources, Collibra Data Lineage now provides lineage for manual parametrised pipeline runs.
- SQL files with WHERE clauses that contain a huge number of conditions no longer cause out-of-memory errors.
- The last sync time is now correctly populated for custom technical lineage sources, even when only the default source code is present.
March 30, 2025 (collibra-edge-2025.02.56)
Metadata integrations
- The Azure AI Foundry integration via Edge is now available in public beta. When you integrate Azure AI Foundry, you integrate the metadata of AI models and AI agents from Azure AI Foundry to the Collibra Platform. The resulting assets represent the Azure AI Foundry model and agent.
For information, go to About the Azure AI Foundry integration via Edge. - With the release of SAP version 2025.5, when integrating SAP Datasphere Catalog, the user who owns the system in SAP Datasphere Catalog must have access to all of the spaces that they want to synchronize in SAP Datasphere Catalog. To own a system:
- You need the “Catalog Admin” permission in SAP Datasphere Catalog.
- You can’t be the System Owner.
Lineage Harvester (CLI and Edge)
- Collibra Data Lineage now ingests lineage from file assets for Google Dataplex.
- Collibra Data Lineage now supports OpenLineage, AWS Glue (via OpenLineage), and Apache Airflow (via OpenLineage) in public beta. This functionality is available on Edge.
For information, go to Create a technical lineage via Edge. - When creating technical lineage for Google Dataplex, column-level lineage support is generally available.
- When integrating MicroStrategy, Collibra Data Lineage now correctly processes data source mapping configurations. You no longer encounter "java.lang.CharSequence.length()" errors.
March 25, 2025 (data-lineage-2025.03.5)
Collibra Data Lineage Service
- We fixed an issue that prevented choosing the correct dialect while processing lineage.
March 24, 2025 (data-lineage-2025.03.4)
Collibra Data Lineage Service
- When ingesting SAP HANA data sources with calculated views, synonyms no longer generate analysis errors.
- When ingesting IBM Db2 data sources, Collibra Data Lineage now supports the "CURRENT USER" keyword.
- When integrating Power BI, Collibra Data Lineage now correctly constructs URLs for embedded Power BI reports in Power BI apps. These URLs are included on the respective asset pages in Collibra.
- When ingesting Azure Data Factory,Collibra Data Lineage now "parses pipeline().RunId" correctly.
- When ingesting Informatica PowerCenter, Collibra Data Lineage has improved support for SQL statement analysis.
- When ingesting data sources, Collibra Data Lineage now generates an analyze error for unsupported JDBC connectors.
March 23, 2025 (collibra-edge-2025.02.49)
Metadata integrations
- When ingesting SAP Datasphere metadata as part of the SAP Datasphere Catalog integration, we now ingest the URLs for the following asset types. The URLs point to the instances of the assets the data builder.
- SAP Datasphere Analytic Model
- SAP Datasphere Intelligent Lookup
- Table
- Database View
- We improved the clarity of Azure ML capability logs.
Lineage Harvester (CLI and Edge)
- Collibra Data Lineage now includes transformation source code in the technical lineage viewer for Databricks Unity Catalog.
- Collibra Data Lineage now ingests table-level lineage for Databricks Unity Catalog.
March 17, 2025 (data-lineage-2025.03.3)
Collibra Data Lineage Service
- When ingesting Informatica Intelligent Cloud Services (IICS) data sources, Collibra Data Lineage now uses the source or output file name from "sessionProperties", if available, as the file or table name.
March 16, 2025 (collibra-edge-2025.02.42)
Infrastructure
- When you install an Edge site on a managed Kubernetes cluster, you can now:
- Configure custom priority classes.
- Skip the configuration of priority classes.Warning We don't recommend configuring or skipping priority classes unless you have an experienced Kubernetes engineer in your organization, as doing so may result in Edge site failures.
- When you run a JDBC Commercial offering capability from an Edge site, the log files are stored when the capability fails or succeeds.
Metadata integrations
- When you ingest Excel files from a local system via an Edge capability, the capability now successfully ingests the files metadata.
Lineage Harvester (CLI and Edge)
- When ingesting Azure Synapse Analytics data sources, you can now choose between two Edge capabilities, depending on whether you want to ingest metadata from one database or multiple databases.
- Use the existing “Technical Lineage for Azure” capability to harvest metadata from a single database (dedicated SQL pool).
- Use the new “Technical Lineage for Azure (multi-DB)” capability to harvest metadata from multiple databases (serverless SQL pool).
- When ingesting Azure Data Factory data sources, Collibra Data Lineage now supports pipeline run data.
- When harvesting Azure synapse data sources, Collibra Data Lineage now supports multiple databases in one capability.
March 10, 2025 (data-lineage-2025.03.2)
Collibra Data Lineage Service
- When ingesting DataStage, Collibra Data Lineage now removes leading and trailing whitespace from the "TableName" tag in the XML definition when extracting schema and table information.
- When integrating MicroStrategy, if project permissions are missing, the integration no longer fails. Instead, an analyze error is generated.
- We fixed an issue so that when integrating MicroStrategy, Collibra Data Lineage now creates relations of the type “Data Attribute used in / uses Report” between MicroStrategy Data Attribute assets and MicroStrategy Report assets, when the data attribute is a Metric.
- When ingesting Snowflake data sources, Collibra Data Lineage now supports:
- Table functions in CALL parameters.
- EXPLAIN statements.
- When integrating PowerCenter, the integration no longer fails if Collibra Data Lineage doesn't receive a value for the shared attribute in the Folder.
- When integrating SAP Hana calculated views, Collibra Data Lineage now supports columns coming from synonyms used in joins.
March 9, 2025 (collibra-edge-2025.02.35)
Security
- We've improved the security of capabilities via Edge.
Metadata integrations
- The Unified Data Classification process no longer collects sample data if the data classes don’t include any "regular expression for data" or "list of values for data" classification rules. It also skips sample data collection if classifications can be based on "regular expression for column names" or "data type" classification rules. This update allows you to classify data without collecting sample data.
- When adding the Edge data classification capability for a data source, you can now define separate timeout parameters. For example, in "Other settings", you can use the "table-sampling-queries-timeout" and "table-sampling-queries-timeout-unit" parameters to specify the timeout for querying samples from the data source.
- For schemas integrated using an earlier version of the Databricks Unity Catalog integration, domains with spaces in their names will remain unchanged. Duplicate empty domains without spaces will no longer be created in future integrations.
- When you synchronize with Azure ML, access tokens are now refreshed to reduce failures if the synchronization takes longer than an hour to complete.
Lineage Harvester (CLI and Edge)
- Collibra Data Lineage now supports the OAuth authentication type, via the Technical Lineage Edge capabilities, to authenticate connections to the Collibra Data Lineage service instances.
March 3, 2025 (data-lineage-2025.03.1)
Collibra Data Lineage Service
- When ingesting Azure Data Factory data sources, Collibra Data Lineage now improved the parsing for expressions.
- When integrating DataStage, Collibra Data Lineage now supports virtual database connections.
- When integrating SSRS, integration no longer fails if Collibra Data Lineage can't find a referenced data source. Instead, an analyze error is generated.
- When ingesting JDBC data sources, Collibra Data Lineage no longer creates duplicate transformations when indirect lineage is involved.
- When ingesting Teradata data sources, Collibra Data Lineage now supports:
- PIVOT statements with string literals.
- BEGIN statements.
- EXPAND ON statements.
- When integrating MicroStrategy, Collibra Data Lineage now correctly creates stitching for dossiers.
- After integrating Tableau, if you hover your pointer over a “TDM” node in the technical lineage graph, the correct label “Tableau Data Model” is now shown.
- When ingesting Snowflake data sources, Collibra Data Lineage now supports chained LATERAL clauses.
- We improved the performance of the SQL statement ordering algorithm, to mitigate the risk of out-of-memory errors during batch analysis.
- When integrating Power BI with DAX analysis enabled, Collibra Data Lineage now correctly identifies the implicit current table in DAX queries.
March 2, 2025 (collibra-edge-2025.02.28)
Infrastructure
- All Edge site pods now have static labels, which allow you to better track your Edge site capabilities.
- The Edge CLI is now automatically installed with new Edge site installations.
Security
- We've improved the security of Edge and capabilities via Edge.
Metadata integrations
- We improved the "Catalog JDBC ingestion" capability to address issues that could occur when synchronizing an empty schema.
- When creating technical lineage for Databricks Unity Catalog, the SQL transformation code is no longer ingested. We plan to reintroduce this support in a future release.
- Foreign keys with the same name but belonging to different tables are now synchronized correctly via the scalable ingestion flow. The foreign key naming convention has been updated to: "edgeConnectionName>jdbccatalog>schemaName>tableName>foreignKeyName (foreign key)."
Lineage Harvester (CLI and Edge)
- When ingesting dbt Cloud data sources, Collibra Data Lineage now supports aliases.
- When ingesting data source types that allow for multiple databases (meaning HiveQL, Microsoft SQL Server, MySQL, Netezza, Spark SQL, Sybase and Teradata), you can now use the optional “Database name JSON” field in your technical lineage Edge capabilities, to provide multiple database names in a list format.
- Collibra Data Lineage now supports the OAuth authentication type, via the Technical Lineage Edge capabilities, to authenticate connections to the Collibra Data Lineage service instances.
February 24, 2025 (data-lineage-2025.02.4)
Collibra Data Lineage Service
- When ingesting dbt data sources, Collibra Data Lineage now supports SQL statements that include CTEs and the "LOCKING" keyword.
- We optimized the creation of lineage relations for large technical lineage graphs.
- When ingesting IICS data sources, Collibra Data Lineage now applies SQL queries defined in mapping configuration task files only to transformations which are assigned to the same connection.
- Collibra Data Lineage now includes transformation source code in the technical lineage viewer for Databricks.
- When ingesting Oracle data sources, Collibra Data Lineage now:
- Generates a single analysis error if the required database link mapping configuration is not provided. The analyze error includes detailed information about the missing configuration.
- Supports database link mapping with multiple links under the same scope.
- We fixed an issue that occurred during Tableau integration, whereby Collibra Data Lineage was using incorrect database columns as source columns.
- When integrating Looker, Collibra Data Lineage now creates a relation of the type "Data Element sources / targets Data Element" between Looker Report Attribute assets and Column assets. (idea #LINA-I-39)
February 22, 2025 (collibra-edge-2025.02.20)
Infrastructure
- Edge now supports using proxy certificates that have a negative serial number. To get this feature support, you must download the new Edge site installer.Note This support is offered to customers with older proxy certificates, which may still have negative serial numbers. However, we don't recommend using a proxy certificate with a negative serial number, as this is no longer best practice and is considered invalid according to the X.509 standard (RFC 5280). As such, Edge will remove this support by the end of 2025. If your proxy certificates have negative serial numbers, update your certificates before the end of 2025.
Security
- We've improved the security of integrations via Edge.
Metadata integrations
- The MLflow integration via Edge is now available in public beta. When you integrate MLflow, you integrate the metadata of ML models from MLflow to Collibra Data Intelligence Platform. The resulting assets represent the MLflow model.
- Collibra Data Lineage now includes transformation source code in the technical lineage viewer for Databricks.
- You can now select "us" and "eu" from the "Location" field when you configure the synchronization of the Dataplex Catalog ingestion.
- In the Databricks Unity Catalog synchronization configuration, you can now define how the compute resource reacts after source tags are extracted. If the "Stop Compute Resource" field is set to "Yes," the compute resource is stopped by the integration. When set to "No," the compute resource remains active.
Protect
- Protect for BigQuery now sets retry parameters for all Google APIs. This ensures that operations such as setting or clearing IAM members on policy tags are retried if a service is temporarily unavailable.
February 17, 2025 (data-lineage-2025.02.3)
Collibra Data Lineage Service
- When integrating Power BI with DAX analysis enabled, an improvement to the caching mechanism allows for faster processing.
- When ingesting Oracle data sources, Collibra Data Lineage now:
- Supports the SYSTIMESTAMP function.
- Supports FETCH statements in CURSORS.
- When ingesting SQL Server data sources, Collibra Data Lineage now supports "LOAD" as a column name.
- When ingesting BigQuery data sources, Collibra Data Lineage now correctly handles SQL statements that contain a lot of common table expressions and wildcards.
- When ingesting Snowflake data sources using the SQL-API mode, Collibra Data Lineage now ignores object types that are not columns in the modified objects returned by Snowflake.
- We added the new "aws-me" Collibra Data Lineage service instance.
February 11, 2025 (data-lineage-2025.02.2.1)
Collibra Data Lineage Service
- We fixed an issue that was causing telemetry data to not be exported properly. Telemetry data are traces and metrics that our Support teams use to help resolve issues.
February 10, 2025 (data-lineage-2025.02.2)
Collibra Data Lineage Service
- When creating a custom technical lineage:
- Collibra Data Lineage now raises an analysis error when the "props" attribute is defined for a column, in a database > schema > table hierarchy.
- Collibra Data Lineage now raises an analysis error if the “useCollibraSystemName” property is set to “false”, but a system is specified in the JSON file.
- When ingesting Teradata data sources, Collibra Data Lineage now supports UPDATE statements inside TRANSACTIONS.
- When ingesting Teradata data sources via shared storage connection (if via Edge) or folder connection (if via CLI harvester), Collibra Data Lineage now offers better support for scenarios involving auto-generated DDL in combination with user-provided DDL statements.
- When integrating Tableau, Collibra Data Lineage now correctly handles database mapping for databases with multiple schemas.
- When ingesting Snowflake data sources using SQL-API mode, the Collibra Data Lineage does not create lineage anymore between base object and direct object.
- When ingesting Azure Data Factory data sources, Collibra Data Lineage now groups the analysis errors that are related to activity output not being supported.
- When integrating Informatica Intelligent Cloud Services (IICS), Collibra Data Lineage now also creates lineage when the "createTaret" attribute is set to "False" in a transformation definition.
- Collibra Data Lineage now fetches information from the Dataplex API differently to prevent failures.
February 9, 2025 (collibra-edge-2025.02.7)
Security
- We have improved the security of capabilities via Edge.
Metadata integrations
- For assets in SAP Datasphere Catalog that have a "summary" and a "description", if the API returns both of these values, they are now both shown in the "Description from Source System" attribute on the respective asset pages in Collibra Data Catalog. To differentiate between the two, the value of the "summary" attribute in SAP Datasphere Catalog is shown with the prefix "summary:".
- You can now configure which initial status you want your SAP assets to have when they are ingested via our SAP Datasphere Catalog integration. This enhancement gives you the same control over SAP-related asset types as exists for all other asset types.
- Google Dataplex Catalog integration now ingests columns for views.
- The ADLS with Purview integration now synchronizes correctly when the "Max Schema Level" field in the capability is set to a value other than 1.
- You can again synchronize Snowflake data sources when the "Include Source Tags" option is selected in synchronization rules.