Release 2025.04

Release information

  • Publication dates:
    • April 1, 2025: Documentation Center and release notes
  • Release dates of Collibra Platform:
    • April 6, 2025: Collibra 2025.04.0 (Upgrade non-production environments)
    • April 27, 2025: Collibra 2025.04.0 (Upgrade production environment )
  • Collibra Cloud for Government
    • April 28, 2024: 2024.11.0
    These dates indicate the day on which you can request your environment to be upgraded. You will not be upgraded automatically.
  • Edge and Data Lineage updates
    • March 31, 2025: Data Lineage 2025.03.6
    • March 30, 2025: Edge 2025.02.56
    • March 25, 2025: Data Lineage 2025.03.5
    • March 24, 2025: Data Lineage 2025.03.4
    • March 23, 2025: Edge 2025.02.49
    • March 10, 2025: Data Lineage 2025.03.2
    • March 16, 2025: Edge 2025.02.42
    • March 9, 2025: Edge 2025.02.35
    • March 3, 2025: Data Lineage 2025.03.1
    • March 2, 2025: Edge 2025.02.28
    • February 24, 2025: Data Lineage 2025.02.4
    • February 22, 2025: Edge 2025.02.20
    • February 17, 2025: Data Lineage 2025.02.3
    • February 11, 2025: Data Lineage 2025.02.2.1
    • February 10, 2025: Data Lineage 2025.02.2
    • February 9, 2025: Edge 2025.02.7
Ticket Product Area Type Content UI Beta Not CPSH Not GovCloud Related topic Idea
DEV-125310 Administrative General settings New and improved To facilitate enterprise-wide adoption, we made minor refinements to how the new license model implements the "Export" global permissions.            
DEV-125235 Administrative Operating model Fixed The global create dialog box now supports asset names longer than 255 characters. latest          
DEV-122511 Administrative Operating model New and improved You now receive error or success messages when deleting an asset type from "Settings" → "Operating Model" → "Asset types." latest          
DEV-122457 Administrative General settings New and improved You now see the same Collibra version number across the product interface.            
DEV-122034 Administrative Operating model Fixed The values of selection attribute types in "Settings" → "Operating Model" → "Attribute types" retain again the order they are created in instead of appearing in alphabetical order. latest          
DEV-121428 Administrative Operating model New and improved The assigned maximum cardinality for all Boolean attribute types that was not 0 or 1 is now 1. Creating or modifying an assignment that sets the maximum cardinality of Boolean attribute types via an API to anything other than 0 or 1 results in an error. Migrating an assignment with Boolean attribute types that have a cardinality higher than 1 changes the cardinality to 1.            
DEV-120826 Administrative Operating model Fixed The "Name" column of a migration import report now contains the asset type name instead of the public ID and mentions the scope name.            
DEV-120826 Administrative Operating model New and improved The "Properties Changed" column of the "Changed Resources" sheet of a migration import report now shows "Asset Page Layout" for asset page layouts.            
DEV-119983 Administrative Import and export New and improved You can now use the option to "Truncate long values" when exporting to Excel when cell values exceed the supported length. latest          
DEV-119937 Administrative General settings Fixed Selecting all activities on a page showing 500 activities and scrolling no longer causes selection and display issues.            
DEV-115533 Administrative General settings Fixed You can no longer select an activity with the status "Canceling" for deletion.            
DEV-114562 Administrative Users and subscriptions Fixed The "License Change History" table captures again changes caused by deleting users.            
DEV-114430 Administrative Users and subscriptions New and improved Users with their status set to "Disabled" are clearly marked as such in the product interface of environments on the new license model. latest          
DEV-114428 Administrative Users and subscriptions New and improved User profiles in environments on the new license model now show the type of license the user has. latest          
DEV-122862 AI Governance   New and improved

When registering an AI use case, the “Register AI Use Case” dialog box now includes a mandatory “Description” field, for providing a description of the AI use case.

Note Prior to Collibra 2025.04, you could provide a description of the AI use case in the Business Context assessment. As of Collibra 2025.04, a description question is no longer included in the Business Context assessment; you now provide a description when registering a new AI use case. Therefore, if you registered an AI use case prior to the release of Collibra 2025.04, but don’t start the Business Context assessment until after upgrading to Collibra 2025.04, you need to manually provide a description on the AI Use Case asset page. Please update any custom workflows that may be affected by this change.

 latest       Register an AI use case  
DEV-121015 AI Governance   Fixed

When registering an AI use case and selecting the domain in which to create the new AI Use Case asset, the “Domain” drop-down list again works as intended. Specifically:

  • Relevant domains are shown in alphabetical order.
  • If you select a domain but change your mind, you can search for and select a different domain.

latest       Register an AI use case  
DEV-120995 API   New and improved The "/rest/2.0/jobs" endpoints of the REST Core API v2 are deprecated in favor of the REST Job API v1.         Collibra Job REST API  
DEV-120506 API   New and improved The REST Import API v2 now generates a more meaningful error message in the logs when importing mappings associated with resources that can't be identified.            
DEV-124893 Assessments   Fixed You can now submit assessments without filling optional date fields. latest          
DEV-122918 Assessments   Fixed The name of the Assessment Review asset created from an assessment on an asset again includes the asset's display name instead of its full name. latest          
DEV-120366 Assessments   New and improved When copying the response of a Checkbox or Radio Button field to a selection-type attribute, you can now replace all field options with the attribute's allowed values. This ensures compatibility between field options and attribute values. latest       Copy response to asset AG-220
DEV-118257 Assessments   New and improved You can now set the maximum number of characters that can be entered in single-line and multi-line text boxes in assessments using the new "Maximum character limit" setting in templates. latest         AG-170
DEV-117643 Assessments   New and improved You can now assign scores to the options in "Checkbox" and "Radio Button" fields in a template, as well as to the "No" option in "Yes/No" and "Yes/No With Reason" fields. These changes allow for more advanced scoring logic, including negative numbers, to meet your diverse scoring needs. latest       Scores and decisions AG-161, AG-197, AG-231
DEV-112564 Assessments   Fixed Expression values are now included in the assessment answers returned through Public API.            
DEV-122889 Collibra Browser Extension   Fixed Tableau pages now load properly when using the extension with a preconfigured Tableau domain.            
DEV-116713 Collibra Browser Extension   Fixed The search page in the extension now shows only saved filters from the search page in Collibra. If you have the "Data Marketplace" global permission, the extension also shows the search tabs as filters. latest       Data Marketplace in Search  
DEV-124022 Data Catalog and Data Source Integrations   Fixed The "Database synchronization report" (beta) now correctly opens when a deleted user ran the synchronization, instead of showing an error. latest   true true Synchronization reporting  
DEV-122700 Data Catalog and Data Source Integrations   Fixed When you remove a description from a Catalog asset page, the "Description" attribute is now also removed, not just its value. classic          
DEV-122699 Data Catalog and Data Source Integrations   Fixed The "Data Source Type" attribute for Google BigQuery and Azure Synapse data sources is now accurate.            
DEV-122004 Data Catalog and Data Source Integrations   Fixed The database synchronization via Edge with the scalable ingestion flow no longer removes "URL" attributes from Table assets.     true true    
DEV-121909 Data Catalog and Data Source Integrations   New and improved You can now accept all or some Collibra AI-generated descriptions for table columns in one action. This update makes it easier to add descriptions to columns. latest   true true Create descriptions for columns in a table with Collibra AI  
DEV-121886 Data Catalog and Data Source Integrations   New and improved You can now define a regular expression to group similar files into a File Group asset during an S3 integration. For example, the (\w*)_\d\d\d\d\.csv regex automatically detects files matching this pattern and groups them into a File Group asset. latest       Create a crawler  
DEV-121194 Data Catalog and Data Source Integrations   Fixed The sampling job on the "Activities" page now reports an error when the sample query fails on Edge. latest          
DEV-120476 Data Catalog and Data Source Integrations   Fixed The memory resources required for the Catalog recommender features are now reduced, improving Collibra Platform performance.     true      
DEV-117939 Data Catalog and Data Source Integrations   New and improved The following Console settings are now moved to a new location:
  • The "Unified Classification enabled" and "Unified Classification migration tool enabled" settings are available in the "Classification" section.
  • "Sampling optimization enabled" is available in the newly added "Sampling" section.
  • "Generate descriptions with Collibra AI" is located in the "Generative AI" section.
         Collibra service configuration options  
DEV-110074 Data Catalog and Data Source Integrations   New and improved Sampling, profiling, and classification are now supported for Databricks Unity Catalog integrations. This simplifies the configuration process and improves efficiency by allowing you to profile and classify data, or show sample data, without registering databases individually. latest beta     Documentation will be available soon DCC-I-2778
DEV-109414 Data Catalog and Data Source Integrations   Fixed You can again use keyboard shortcuts when working on Collibra AI-generated descriptions. latest   true true    
DEV-123871 Data Marketplace   Fixed In standalone Data Marketplace, the "Filters" pane now shows the "Filter Name" instead of the "Filter ID."            
DEV-122891 Data Marketplace   Fixed We improved the user experience when you change the availability or collapse status of a filter facet on the "Filter Facets" page.

            
DEV-119731 Data Marketplace   New and improved Asset previews in both standalone Data Marketplace and Data Marketplace in Search now show relations assigned through an asset type group.            
DEV-124585 Data Notebook   New and improved The "Data Explorer" section of a data notebook now shows the description from the source if an asset description isn't available. latest          
DEV-122157 Edge   New and improved We improved our Edge site logs to better identify when connections, capabilities, and secrets have been deleted. latest          
DEV-10642 Edge   New and improved When harvesting JDBC sources using lineage via Edge, the lineage capabilities now provide better visible distinction between the default SQL and customized statements. latest          
CFT-3054 General Text editor New and improved The "Code Block" style in the "Paragraph" drop-down list in text editors is now renamed "Preformatted." It changes the paragraphs into preformatted text using the <pre> tag. Preformatted text also supports hyperlinks.

A new icon is added to the formatting toolbar in text editors to create a code block. When you use a code block, all text formatting options are automatically disabled to maintain code integrity.

 latest       Text editors  
DEV-124484 CFT-3805 CFT-3810 CFT-3831 DEV-118237 General   New and improved With 2025.04, you’ll notice several enhancements to the latest UI aimed at improving consistency, stability, and user experience.
  • Updates to the layout of pages and components:
    • Actions and pinned workflows are now always positioned on the right side as the last item.
    • You can now collapse the left sidebar on pages such as the "Overview" tab on asset pages, the "Usage Analytics" page, the "Profile" page, and the "Search results" page.

  • Improved responsiveness:
    The Collibra Platform is now more responsive, making interactions on smaller screens easier. For example, the top navigation bar adapts better to different screen sizes.
  • Accessibility improvements:
    We improved accessibility across the Collibra Platform to align with WCAG 2.2 guidelines, enhancing inclusivity. For example, on the "Profile" page on the "Responsibilities" tab, you now click the icon instead of the header to expand or collapse the area. This change makes it easier for screen readers to access all information and interact with this component.

latest          
DEV-123383 General Views Fixed You can no longer delete a view that is set as the Domain Type Default View (beta). latest       Set a domain type default view (beta)  
DEV-122755 General Asset management Fixed Long role names in tiles now wrap to a new line, staying within the tiles' boundaries and eliminating horizontal scroll bars. latest          
DEV-120025 General Asset management Fixed When moving an asset to another domain, the breadcrumb is now properly updated without requiring a page refresh. latest          
DEV-119462 General Dashboards New and improved You can now enable enhanced CSRF protection for custom HTML dashboards that use HTTP requests other than GET. A new "Trust this iFrame source" checkbox is available for Embedded Webpage and Collibra Insights widgets in the latest UI, and for Collibra Insight widgets in the classic UI.          
DEV-118899 General Text editor Fixed When using the text editor within a dialog box, you can now switch from HTML mode to rich text mode without the dialog box closing, even if there is an incompatible value. latest          
DEV-118300 General Dashboards Fixed When you change the name or description of a dashboard, the changes are now immediately reflected in the "Browse" pane. latest          
DEV-105690 General Asset management Fixed If the account of a user who created or last modified an asset is deleted, the "Created By" and "Last modified by" fields for the asset in an asset view now show an appropriate message instead of being empty. latest          
DEV-123969 Protect   Fixed Protect synchronization using custom data sources no longer results in an error.            
DEV-123304 Protect   New and improved You can now manually start a full synchronization of policies using the "Sync Policies" button. The button appears on the "Data Protection Standards" and "Data Access Rules" tabs only if you have the "Protect" > "Edit" or "Administration" global permission. latest          
DEV-123304 Protect   New and improved Protect now allows lazy sync, which synchronizes policies to a data source only when there are actual changes in policies or assets to be masked. This reduces the load on your data warehouse. The full sync option is still available, and both schedules can be configured by administrators in Collibra Console.         Protect synchronization  
DEV-6454 Protect   New and improved You can now access data protection standards and data access rules with a dedicated URL, allowing easier collaboration around such policies. latest          
DEV-123528 Search   Fixed If you select a saved filter that uses a deleted asset type, the asset type is now excluded from the filter and the search page no longer crashes. latest          
DEV-123488 Search   Fixed Reindex jobs no longer continuously fail due to unexpected timeouts.            
DEV-123272 DEV-122253 Search   New and improved Quick search now shows up to 5 results instead of 3, saving you time and effort. These results include 2 top matches and up to 3 recently visited assets that match your text. If fewer than 3 recently visited assets match, the remaining spots are filled with top matches. Additionally, top matches, which were previously based only on the "Name" field, now also consider the "Description" and "Definition" fields to deliver more relevant and meaningful results. latest       Quick search  
DEV-123130 Search   Fixed The "Asset Type" facet on the search page no longer shows incorrect count next to each asset type under certain circumstances. latest          
DEV-123112 Search   New and improved If your search text within a facet contains more than one word, the space between the words is no longer treated as a logical OR. For example, searching for "Data Quality" in the "Asset Type" facet shows results such as "Data Quality" and "Data Quality Metric," but not "Business Quality." latest         DIP-I-599
DEV-119826 Search   Fixed When your search text doesn't match any content but results for the closest match are available, a search in the "Asset Type" facet now shows asset types based on the closest match instead of no results. latest          
DEV-119731 Search   New and improved Asset previews in both standalone Data Marketplace and Data Marketplace in Search now show relations assigned through an asset type group.            
DEV-118281 Search   Fixed When you use quick search from a domain or community page, only assets that belong to that domain or community are now shown as recently visited suggestions. latest       Quick search  
DEV-120825 Usage Analytics   Fixed You can now close the date range picker in the "Usage Period" field on touch-screen devices. latest          
DEV-96842 Workflow Designer   New and improved The "HTTP task" is renamed "External API task" to better reflect its purpose.     true     DCC-I-878
DEV-96842 Workflow Designer   New and improved You can now use the new "Collibra API Task" to build workflows that interact with Collibra REST APIs, extending workflow functions beyond Java and external REST APIs.     true   Collibra API task DCC-I-878
DEV-117301 Workflows   Fixed Workflow tasks with a subform no longer show the subform label twice. latest          
DEV-116355 Workflows   Fixed Starting workflows on multiple assets no longer prevents you from seeing error messages if errors occur. latest          

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.