Only show release notes of Collibra Platform for Government-certified features
Latest UI onlyHide release notes that are only relevant for the classic UI. Learn more 

Release 2024.07

Release information

  • Publication dates:
    • June 24, 2024: Release notes
    • July 4, 2024: Documentation Center
  • Release dates of Collibra Platform:
    • July 7, 2024: Collibra 2024.07.0 (Upgrade non-production environments)
    • July 28, 2024: Collibra 2024.07.3 (Upgrade non-production and production environments)
    • On demand: Collibra 2024.07.4
    • On demand: Collibra 2024.07.5
  • Edge and Data Lineage updates
    • January 26, 2025: Edge 2024.07.203
    • January 19, 2025: Edge 2024.07.196
    • January 12, 2025: Edge 2024.07.189
    • December 15, 2024: Edge 2024.07.161
    • December 1, 2024: Edge 2024.07.147
    • November 24, 2024: Edge 2024.07.140
    • November 17, 2024: Edge 2024.07.133
    • November 10, 2024: Edge 2024.07.126
    • November 3, 2024: Edge 2024.07.119
    • October 20, 2024: Edge 2024.07.105
    • October 6, 2024: Edge 2024.07.91
    • September 30, 2024: Data Lineage 2024.09.5
    • September 29, 2024: Edge 2024.07.84
    • September 27, 2024: Data Lineage 2024.09.4.1
    • September 23, 2024: Data Lineage 2024.09.4
    • September 22, 2024: Edge 2024.07.77
    • September 16, 2024: Data Lineage 2024.09.3
    • September 15, 2024: Edge 2024.07.70
    • September 10, 2024: Data Lineage 2024.09.2.1
    • September 9, 2024: Data Lineage 2024.09.2
    • September 8, 2024: Edge 2024.07-63
    • September 1, 2024: Edge 2024.07-56 and Data Lineage 2024.09.1
    • August 24, 2024: Edge 2024.07-48 and Data Lineage 2024.08.4
    • August 18, 2024: Edge 2024.07-42 and Data Lineage 2024.08.3
    • August 11, 2024: Edge 2024.07-35 and Data Lineage 2024.08.2
    • August 4, 2024: Edge 2024.07-28 and Data Lineage 2024.08.1
    • July 27, 2024: Edge 2024.07-20 and Data Lineage 2024.07.5
    • July 25, 2025: Data Lineage 2024.07.4.1
    • July 21, 2024: Edge 2024.07-14 and Data Lineage 2024.07.4
    • July 14, 2024: Edge 2024.07-7 and Data Lineage 2024.07.3
    • July 7, 2024: Edge 2024.07-0 and Data Lineage 2024.07.2
    • June 30, 2024: Data Lineage 2024.07.1

Metamodel changes

  • The File Container asset type is renamed "Storage Container" to better reflect the content that this asset type can include. As a result, the associated relation types are updated.

    Important The File Container asset type is currently used in integrations with ADLS, GCS, S3, and SAP Datasphere. Please update any workflows or integrations that reference this asset type by name to ensure they continue to function correctly.

  • The relation type "Asset complies to / applies to Governance Asset" is now part of the AI Use Case and AI Model global assignments. This allows you to create relations between:
    • AI Use Case assets and the Policy assets that govern them.
    • AI Model assets and the Policy assets that govern them.
  • This relation type is not new and is not limited to an AI Governance context.
  • The AWS Sagemaker AI model asset type has been added to the operating model in preparation of the upcoming Amazon SageMaker AI model integration via Edge.
  • The Azure AI model asset type has been added to the operating model in preparation of the upcoming Microsoft Azure AI model integration via Edge.

New features

Data Catalog

  • A migration process for Unified Data Classification is available. The process copies classification information from old, deprecated classification methods into the Unified Data Classification method and creates new data classes based on existing Advanced Data Types (ADTs).
    • If Unified Data Classification was already enabled before 2024.07, nothing changes in your environment.
      If you want to migrate old classification information and ADTs, you can manually start the migration after you have activated the migration setting.
    • If another classification method was in use (old Edge classification or the Cloud Data Classification Platform), we will enable Unified Data Classification and complete the migration process during the 2024.07 upgrade.
      You can, for now, still deactivate Unified Data Classification and restart the migration process later. However, remember that the other classification methods will reach its end of life on September 30, 2024.
    • If the Classification API was used and Unified Data Classification was not enabled, we will enable Unified Data Classification and complete the migration process during the 2024.07 upgrade. You need to update your client applications or workflows that call the API.
      If the Classification API was used and Unified Data Classification was already enabled, nothing changes.
    Note This migration affects Protect. For more information, go to the Protect release note in the Enhancements section below.

Data Lineage and BI integrations

  • The shared database model feature is now generally available. Sharing database models allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This mitigates analysis errors and allows for a complete lineage that includes lineage from the SQL statements from dependent data sources.
  • Technical lineage for Databricks Unity Catalog is now generally available.

AI Governance

  • You can now:
    • Configure which assessment types you want added in the Lifecycle Tracker when a new AI use case is registered.
    • Configure the assessment types to be added in the Lifecycle Tracker when the AI use case evolves from one lifecycle stage to the next, for example from Ideation to Development.

  • “Decision gate” activities are now automatically added to the Lifecycle Tracker when you change the lifecycle stage of an AI use case, for example from Ideation to Development, or vice versa. Decision gates allow you to describe and capture the decisions and justification for advancing or regressing the stage of the use case.
  • You can now add “decision record” activities to the Lifecycle Tracker. Decision records allow you to capture any pertinent information regarding the decisions you and other stakeholders make about the AI use case.
  • Prior to this release, you could only access the Business User landing page or the AI Legal Review landing page, based on your global role. Those landing pages are now the AI Governance landing page and the AI Legal Reviews page, respectively, and you can access either regardless of your global role. You only need access to AI Governance.
  • The following AI Governance-specific workflows are deprecated and are no longer included in Collibra installations. They no longer appear in the Workflow definitions section in the Settings.
    • Register AI Use Case
    • Copy assessment answers to AI Use Case asset
    The functionality previously carried out by these workflows is now integrated in Collibra, instead of being carried out by the workflows. This change does not require any action from you.

Data Governance

  • If you have a new license model, you can now request responsibilities for domains or assets via Actions → Request Responsibility.

Protect

  • You can now create drafts of standards and rules using the new "Create Draft" button. This allows you to work on a standard or rule without immediately starting the sync. (idea #DCC-I-3011)
    Tip To start the sync, you need to click "Publish."

Miscellaneous

  • On the Custom Theme page:
    • You can now customize primary and secondary button colors specifically for a dark background using the new "Primary Button on Dark Background" and "Secondary Button on Dark Background" components.

      Note Your previously customized primary button colors are applied to primary buttons on a light background.
    • The "Secondary Button" component now includes more button types, such as outline buttons, split buttons, and button groups.

      Note Your previously customized secondary button colors are no longer applied. You can customize them again using the updated "Secondary Button" component. When doing so, prioritize readability and accessibility.

Enhancements

Data Catalog

  • When Unified Data Classification is activated, the Catalog profiling process no longer starts the old Edge classification process automatically.
  • You can now easily view the structure of Array and Struct technical data types by clicking "View Array" or "View Struct" in the "At a Glance" pane on Column asset pages, or in tables on asset pages and asset views.
  • The Catalog Recommender is enhanced to improve its performance and efficiency:
    • When the "Catalog Recommender Enabled" setting is disabled, data similarities are no longer computed. This may result in a delay for customers who re-enable the Recommender as similarities are recalculated.
    • The recommender process now automatically removes old events, helping to reduce disk space and memory consumption.
  • We now support copying existing synchronization rules between schemas. In Catalog, you can streamline a database synchronization configuration by copying existing synchronization rules from one schema to other schemas. This saves time and ensures consistency in the synchronization configuration. (idea #DCC-I-739)
  • You can now use the “Tableau API timeout” setting in Collibra Console to limit how long (in seconds) an HTTP connection between Collibra and a remote Tableau server will stay open when there is no response from the Tableau server. The default value is 600 seconds.
    Note This setting applies only to Tableau integrations via Jobserver. The end of life of Jobserver and all related Jobserver integrations has been announced for September 30, 2024. This means that the Tableau via Jobserver integration method is deprecated and will also reach its end of life on September 30, 2024.
  • To make the process of checking the Edge cache for samples much faster, the "Sampling optimization enabled" setting is now enabled by default in all environments.
  • When you integrate Google Dataplex, the URL is now synchronized for the Dataplex Lake and Dataplex Zone.

Data Governance

  • Rebuilding automatic hyperlinks is now available only .

  • You can now enable or disable downloading and uploading attachments. Contact Collibra Support for more information.
  • Collections are now generally available. Collections allow you to group assets into organized lists. They help you work more efficiently because they give easy access to the assets you need.
  • You can now upload images into text attributes on asset pages. This prevents the issue of reaching your allowed character limit too quickly.
  • Script attributes now apply syntax highlighting for better readability.
  • In the asset type layout editor, sysadmins can now view the characteristic type description while editing the layout.
  • The AI Use Case placeholder is shown on your editor layout and the content is filled in by Collibra.
  • Within the Operating Model pages of the Collibra Settings, you can now view the public IDs of asset types, attribute types, relation types, complex relation types, domain types, and scopes. If they are not protected, you can also edit the public ID.
  • When you create an articulation score rule with a status in the Condition Value field, suggested statuses are shown first. If the status you want is not in those options, you can also view all the statuses.
  • We improved the loading time of the "Assets" tab on domain pages when the view contains a very large amount of assets with many complex relations.
  • We improved the performance of sorting by responsibilities for views with a very large amount of assets.
  • For a seamless import experience, during an export, Collibra now translates the asset table headers that the import wizard uses to perform auto-mapping.

Assessments

  • When editing an assessment, you can now use the new "Cancel" button to view the entire assessment, without having to reopen it from the landing page.
  • The "Copy" button in an assessment is now renamed "Retake" to better describe its purpose. The button still allows you to duplicate an assessment in the Draft status. You can also retake an assessment from the Assessments landing page and the Assessment Review asset page using the new "Retake Assessment" button.
    Note An assessment can be retaken even if the template used in the original assessment isn't the latest. The new assessment, however, always uses the latest version of the template.
  • When using an asset picker in an assessment, you can now filter the assets by communities and domains using the new "Filter Assets by Organization" checkbox.
  • When configuring an asset picker in a template, you can now specify multiple asset types, include child asset types, and specify asset statuses, giving you more control and flexibility over asset selection.
  • Properties in an assessment are now shown in a sidebar instead of a tab, making them easier to find.
  • You can now delete a custom template only if it's not used in an assessment that's in the Draft status.
  • When configuring an asset picker in a template, you can now specify multiple asset types, broadening the range of assets available in an assessment.

Protect

  • As a result of the migration to Unified Data Classification, the following changes occur in Protect:
    • If data classes were previously used in standards and rules, they are removed from them.
      Important To mitigate this loss, before the migration, capture the data classes used in standards and rules. After the migration, you can add those data classes back to the standards and rules.
    • The synchronization statuses of active standards and rules that use data classes change from "Active" to "Failed" upon the next synchronization.
      Important Although the synchronization status shows “Failed,” such standards and rules continue to be enforced in data sources, ensuring ongoing data protection.
    • For more information, go to the Support Portal.
  • On the “Groups” tab, you can now filter the groups by group name and system reference, and sort the groups by group name and created date.

Workflows

  • Uploading a workflow with a modified description now updates the description saved in Collibra.

Workflow Designer

Note Workflow Designer enhancements become available with the upgrade of production environments.

  • You can now add a domain type filter to the Domain Collibra data entry component by specifying the ID of a domain type in the "Domain type ID" field. (idea #DCC-I-1315)
  • You can now include assets from meta domains and meta asset types in the Asset and Asset type Collibra data entry components by clearing the "Exclude meta" filter.

Edge

  •  We now support the following versions for our managed Kubernetes clusters:
    • AKS 1.29
    • AWS Fargate using EKS 1.29
    • EKS 1.29
    • GKE 1.29
    • OpenShift 4.15

Search

  • If your search text doesn't match any existing content, results are now shown for the closest matching text. This increases the chances of finding the correct information, even with typographical errors in the search text.
  • If you don't have permission to create a search filter, you're no longer presented with the option to create one.

Usage Analytics

Note Usage Analytics enhancements become available 1-2 days after the upgrade of environments.

  • The “Most Visited Assets” section now shows asset names along with their asset type icons and symbols, making it easier to identify and distinguish assets without having to open each one.
  • Legend selections on charts are now retained when updating filters, simplifying the comparison of metrics across different filters without having to reselect the legends.

Collibra Console

  • You can now use the "Backup compression level" console configuration option to choose the level of compression for backups.

API

Miscellaneous

  • If you have a new license model, you can now download a "License assets usage report" from Settings → Users and Subscriptions → Assets. The report contains weekly historical data of the asset allowance and consumption.

Fixes

Data Catalog

  • The "Empty Value Count" field in the profiling information of an asset now shows the correct percentage. For example, we now show 33% instead of the incorrect value 0.33%.
  •  In Unified Data Classification, the side pane now closes if you delete the data class you're currently viewing.
  • The deletion process for data classes is now updated to allow for successful deletion of classes that were used to classify multiple columns.
  • You can now start only one classification job at a time for the same data. If a previous job is already running or queued, you won't be able to start another job for that data. (idea #DCC-I-5693)
  • The GET /rest/catalog/1.0/dataClassification/classificationMatches/bulk endpoint in the REST Classifications API v1 is updated to ensure accurate retrieval of classifications based on the specified offset and limit parameters. Previously, the endpoint rounded the offset value, which resulted in incorrect classifications being returned.
  • The REST Classifications API v2 is updated. The lastModifiedBy and lastModifiedOn parameters for a classification are now accurately updated whenever a classification is changed.
  • The Catalog Database Registration REST API is updated. The GET /rest/catalogDatabase/v1/databaseConnections endpoint no longer returns databases from deleted Edge connections.
  • Edge can now profile PostgreSQL tables that contain null values in decimal or numeric columns without any issues. Previously, the profiling of the whole table failed and the table was skipped.
  • To prevent the sampling and profiling processes from stopping, Edge now handles invalid dates in tables, for example, 0000-30-30, differently.
    • When collecting samples, invalid values are replaced with "Invalid value."
    • During profiling, invalid values are ignored.

    This change mainly impacts Amazon Athena, as most data sources typically handle data type validation themselves.

  • The workflow Start Events "Database Registration Completed" and "Database Registration Failed" now correctly trigger workflows after the Database Synchronization jobs via Edge have finished.

Data Governance

  • We improved the text editor:
    • When you add plain text, the text editor no longer automatically wraps the text in HTML markup. This provides a cleaner and more intuitive experience.
    • When you apply formatting, such as bold, a new line, or a list, the text editor now consistently applies HTML markup to the entire block of text, including the beginning and the end.
  • The global and resource roles tables in Settings → Users and Subscriptions no longer fail to show the "Name" and "Description" columns in some rare cases.
  • To provide you with the necessary data for an informed action, you can now see the details of the users while adding a responsibility to a domain or asset even if "Limit user information access" is enabled in Collibra Console.
  • To avoid size limitations when exporting to Excel, the images you add to asset attributes using the rich text editor are now stored as attachments instead of inline.
  • The text attribute on an asset page is now shown in full width instead of compacted mode when added. This field is shown in full width by default.
  • In community tables, the description is now automatically updated without a manual refresh when changes are made.
  • You can no longer click outside of a text field on Tailored Asset Pages to save your changes. You can save or discard your changes by using the "Save" and "Cancel" buttons.
  • The data quality tab page now loads correctly, even when asset names contain quotes.
  • We improved 'Assets' tab page of the Global Create dialog box. When there is an exact match on asset type name, that item is at the top of the list.
  • The suggested tab containing the asset types relevant for the domain is now shown for users with 'Asset > Add' permissions when they are on a domain page.
  • Opening a workflow definition page no longer results in an error.
  • Some existing out-of-the-box attribute types, and relation types related to Dataplex and Google Cloud Platform had a UUID that was not unique. This could cause issues with, for example, the operating model migration feature. Therefore, we changed the UUIDs of the items in the list below.
  • You can now delete the duplicate relation Type "Data Quality Rule is executed by/executes Data Quality Metric" (ID 00000000-0000-0000-0000-090000010024) can.
  • You can now add large image files to the text editor of attributes.
  • Asset pages no longer automatically scroll to a random place when opened.
  • If you change the name of an out-of-the-box role, you now see it correctly on the title bar of domain and community pages.
  • We improved the breadcrumbs on asset pages to be responsive to your screen size, zoom, and resolution.
  • We fixed a Safari browser related issue for the display of workflow labels.
  • When adding a comment on an asset page with check boxes and saving, the check boxes aren't shown as if they are interactive.
  • Validation results are shown in the activities table and can be opened and downloaded.
  • Encoded organization names are now shown correctly in the history.
  • You can now select all drop-down options on an asset page regardless if the “At a glance” layout is open or not.
  • If you edit complex relation types that are marked as system, the custom leg types or custom attribute types now need a minimum cardinality of 0.
  • We improved hyperlinking when two assets are hyperlinked to a text and one is deleted.
  • We removed the allowed values from 'Retrain Cycle' since it was transformed to a text attribute in the 2024.05 release.
  • If you have a global role with the System Administration global permission, the complex relation type in edit mode no longer has the Delete icon for the system assigned leg types and attribute types.
  • We fixed the complex relation types settings page where the table wasn't showing the values for the Relation IDs column correctly when selected.
  • The "Save" button is removed from tables on the Operating Model section of the Collibra settings because your changes are saved automatically.
  • The tables in the Operating Model section of the Collibra settings now always show the System column.

Data Marketplace

  • Data Marketplace no longer shows search results based on relation indexes that go outside of the defined Data Marketplace scope.

Workflows

  • Starting a workflow with the "StartWorkflowInstancesRequest" builder from an asynchronous script task no longer ignores any form properties that the script task defines.
  • The latest UI now displays regex validation error messages for workflow form fields.
  • The "Rich text" form validation now works as expected in the latest UI. (idea #DCC-I-3087)
  • The "View relevant changes" section of a workflow task is now visible in dialog boxes, in the latest UI.
  • We optimized how the "View relevant changes" section of a workflow task appears in the sidebar, in the latest UI.

Workflow Designer

Note Workflow Designer fixes become available with the upgrade of production environments.

  • After a period of inactivity, you no longer see a connection error and are redirected to the sign-in page instead.

Edge

  • When you install an older Edge site with automatic upgrade enabled that had not been previously installed, the Edge site now installs with the most recent version of Edge.
  • When you install an Edge site via the Edge CLI method, connectivity checks for a forward proxy are now included.

  • The Connections tab now loads successfully for offline Edge sites that use Vault integrations.
  • If you click the JDBC log file download button multiple times, it no longer starts multiple downloads.
  • When you migrate an Edge site with a Shared Storage connection from k3s to a managed Kubernetes cluster, your Edge site now installs in a healthy state, as expected.
  • You can now select the Shared Storage connection option on an Edge site installed on a managed Kubernetes cluster, as expected.
  • The search filter on the Connections tab of an Edge site now fully loads search results.

Search

  • Relation reindexing no longer fails when a relation type is deleted.

API

  • The "Output Module" resource of the REST Core API v2 no longer returns duplicate results when sorting on a large number of text attributes, some of which differing in casing.

Miscellaneous

  • Adding a photo to an SSO, LDAP, or SCIM user profile no longer causes an error.
  • You can no longer edit the user name of an SSO, LDAP, or SCIM account.
  • Collibra-generated emails no longer show extra characters for local users that have a period in the user name.
  • SCIM provisioned users now have their preferred language set in accordance with the IdP attribute if that language is supported by Collibra.
  • You can now order the items in the Counters and Workflows dashboard widgets using the new drag-and-drop icon, instead of deleting and re-adding the items to change the order.
  • You can now use the keyboard to navigate an auto-complete drop-down menu.
  • If you schedule a job using a cron expression, for example, to synchronize a data source, Collibra DIP now transforms the cron expression to the Unix cron format in the backend. You still have to enter the cron expression in Quartz or Spring format. However, because Unix cron expressions don't include seconds and years, the fields for seconds and years are now ignored.

Featuresin preview

A public preview is an upcoming feature or product that is made available to all customers before it is fully ready for general availability so it can be tested and evaluated early. Learn more
  • The first SAP SAP Datasphere Catalog integrations are now available in preview:
    • SAP Analytics Cloud
    • SAP Datasphere

    You can create a connection to SAP Datasphere Catalog and integrate metadata from SAP Analytics Cloud or SAP Datasphere. We have updated our out-of-the-box operating model with the required asset types for these integrations.

  • If you have a new license model, you can now see the operations that have an impact on the number of assigned seats in Settings → Users and Subscriptions → Seats → License Change History (in preview) → Daily. During the preview period, the table captures the most common actions that lead to a changes in the number of assigned seats, such as editing a resource responsibility or a global role membership, therefore the data might be incomplete.
  • Data Notebook now supports the Oracle data source.

Collibra maintenance updates

Collibra 2024.07.1

  • Task buttons in workflows that are designed with the Eclipse plug-in now retain their original position in the latest UI.
  • Reaching the maximum number of API call log entries no longer prevents Collibra from starting after an upgrade to version 2024.07.
  • We have improved the memory management of Data classification.

Collibra 2024.07.2

  • We improved how Spring and Quartz Cron expressions are transformed to the Unix format in the backend, addressing potential issues during the upgrade.
  • Protect standards now work with all available Data Classification methods.

Collibra 2024.07.3

  • The getResults() method of the PagedResponse object of the Java Core API returns again an ArrayList instead of an ImmutableCollection.
  • You can again reindex Collibra.
  • You can again register data sources via Edge when direct queries are enabled in the Edge configuration and you are using an allowlist in your environment. The registration no longer fails with error "Unable to get a list of databases from the source".
  • When you rerun an integrated dataset with a run ID of a later date and with fewer columns than the initial integration run, you no longer get an "IncorrectResultSizeDataAccessException" error.
  • Starting from a view, you can once again validate or move assets when NIST logging is enabled.

Collibra 2024.07.4

  • A feature that optimizes sorting assets by description no longer causes slowness or a timeout error in other scenarios.

Collibra 2024.07.5

  • We fixed issues in an open-source library used in our platform to mitigate memory issues in large Collibra environments. For information on our use of open source software, go to Open source notices and documentation.

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.

January 26, 2025
(collibra-edge-2024.07.203) 

Security

  • We improved the security of lineage capabilities via Edge.

Metadata integrations

  • The technical lineage capability synchronization no longer fails due to large metadata files sent to DIP.

Protect

  • Protect for BigQuery now properly handles project IDs and dataset names that include dashes.

Lineage Harvester (CLI and Edge)

  • When integrating SSRS, Collibra Data Lineage now skips reports for which the configured user does not have sufficient access rights and creates an analyse error.
  • When harvesting Oracle data sources, the memory footprint is now reduced, allowing the lineage harvester to successfully harvest metadata from much larger data sources.

January 19, 2025
(collibra-edge-2024.07.196) 

Protect

  • Protect for Google BigQuery handles non-protected tables being renamed during synchronization.

January 12, 2025
(collibra-edge-2024.07.189) 

Security

  • We improved the security of capabilities via Edge.

Metadata integrations

  • OAuth autentication now works as expected with Edge Proxy for Databricks Unity Catalog.
  • When creating technical lineage for Dataplex, Collibra Data Lineage now ingests interactive queries by default. You can disable the ingestion of interactive queries when synchronizing the capability.

Lineage Harvester (CLI and Edge)

  • When harvesting PBRS data sources, the Collibra Data Lineage now honors the no_proxy configuration.

December 15, 2024
(collibra-edge-2024.10.70) 

Protect

  • Policy tags and associations in BigQuery are now removed from columns that are no longer protected via Protect standards and rules.
  • For AWS Lake Formation, if your Edge version is 2024.07 or newer, clearing the "Grant Access to Data Linked to Selected Assets" checkbox in a rule now creates only a data filter for the tables linked to the assets. This provides better control over data access.
    Note 
    • Selecting the checkbox creates both data filter and data permission.
    • For Edge versions older than 2024.07, both data filter and data permission are created regardless of the checkbox status.
  • Lineage Harvester (CLI and Edge)

    • When harvesting Oracle data sources, Collibra Data Lineage now supports TRIGGERS.
    • When creating a custom technical lineage via the CLI lineage harvester or Edge, using the batch definition method, the lineage harvester now validates the syntax in your JSON files.
    • The lineage harvester (Edge and CLI) and the technical lineageEdge capabilities are using the DNS names documented in Collibra Data Lineage service instances.
    • When harvesting Oracle technical lineage sources, logging can now be enabled in the Edge harvester, to aide troubleshooting. Data object harvesting details are captured in a log file in the metadata batch.
    • The Dataplex lineage can now handle GCS file names which contain wildcards.

    December 1, 2024
    (collibra-edge-2024.07.147) 

    Lineage Harvester (CLI and Edge)

    • The Analyze Only option in the technical lineage Edge capabilities is now deprecated. The functionality is replaced by the new Processing Level drop-down list. This new mandatory setting gives you more control in configuring when metadata is harvested, analysed, and synchronised.
    • When ingesting Snowflake data sources using SQL-API mode, the SQL queries to harvest the data are updated to be more lightweight.
    • When creating a custom technical lineage via the CLI lineage harvester or Edge, using the batch definition method, the lineage harvester now validates the syntax in your JSON files.

    November 24, 2024
    (collibra-edge-2024.07.140) 

    Security

    • We improved the security of integrations via Edge.

    Metadata integrations

    • You can now download the input metadata from the Databricks Unity Catalog Lineage "Synchronization Results" dialog box if you selected the "Save Input Metadata" checkbox when you created the Databricks Unity Catalog Lineage capability.
    • When you synchronize a Vertex AI integration, you can now download the input metadata file from the Sync results dialog box on the Activities page. In order to achieve this, you must select the "Save Input Metadata" checkbox when you create a Vertex AI capability.
    • When registering a Databricks data source, a new domain is now created for each database and schema if they are new and no explicit domain mapping is provided.
      • Databases follow the naming pattern "systemDomainName > databaseName," while schemas follow "databaseDomainName > schemaName."
      • Domain mapping takes precedence over the creation of new domains.
      • Existing Database and Schema assets remain in their current domains.
    • The Dataplex lineage can now handle GCS file names which contain wildcards.

    November 17, 2024
    (collibra-edge-2024.07.133) 

    Collibra Protect

    • To prevent excessively log entries, Protect for BigQuery no longer logs debug messages.
    • BadSqlGrammarException errors reported in Protect for Databricks and Snowflake now include the underlying root cause instead of vague descriptions.

    November 10, 2024
    (collibra-edge-2024.07.126) 

    Security

    • We improved the security of integrations via Edge.

    Data Catalog

    • Dataplex technical lineage now also supports Google Cloud Storage (GCS) assets that have a full name which starts with gcs: in addition to gs:.
    • The AI model integration for Databricks Unity Catalog now correctly handles cases where a model has an associated run that no longer exists.
    • The Databricks Unity Catalog integration now handles errors during synchronization better, ensuring that the synchronization job does not get stuck.
    • The Amazon S3 integration now successfully completes when encountering an AWS Glue table with duplicated column names. The synchronization detects duplicated columns and logs a warning about the duplication, advising you to fix the issue on the data source side. The column position will not be included for these columns.
    • We updated the error message for AWS SageMaker AI integrations in unsupported regions.
    • You can now indicate that you don't want asset statuses to change during a Databricks resynchronization. The Databricks synchronization configuration includes a "Default Asset Status" field. The default value is "Implemented" and is available for all Databricks ingestion types.
      • If "Implemented" is selected, all assets are ingested with "Implemented" status.
      • If "No Status" is selected, all assets are ingested with the first status listed in the Operating Model statuses, and changes will not be overwritten. For example, if you change an asset status from "Candidate" to "Implemented" before the resynchronization, the status remains "Implemented."

    November 3, 2024
    (collibra-edge-2024.07.119) 

    Infrastructure

    • You can now download a new version of the Edge CLI outside the legacy Edge tool. For more information, go to the Edge CLI documentation.
    • Edge sites with a proxy no longer fail or run into issues when updating the proxy settings.

    Lineage Harvester (CLI and Edge)

    • The capability for technical lineage for OpenLineage is now visible in the “capability template” drop-down list, preparing for public availability. Note that only participants in the private preview should use this feature.
    • When ingesting Oracle data sources, the Collibra Data Lineage service instances now support scoped database link names.
    • If Tableau integration fails because of timeout errors due to page sizing limits, Collibra Data Lineage now automatically adjusts the settings and retries.

    October 20, 2024
    (collibra-edge-2024.07-105) 

    Security

    • We have improved the security of Collibra Protect.

    Collibra Protect

    • Protect for Snowflake supports column names containing spaces and special characters.
    • You can now choose how Snowflake checks roles (that is, Protect groups) for applying standards and rules, accommodating Snowflake users who have multiple roles. When adding a capability for Protect for Snowflake, the "Edit Capability" dialog box contains a new "Snowflake role testing" field with the following options:
      • - "CURRENT_ROLE" (default): Checks only the primary role assigned to the Snowflake user.
      • - "IS_ROLE_IN_SESSION": Checks all the roles assigned to the Snowflake user, including secondary roles, within the active session.

    Metadata integrations

    • The Azure ML integration now supports the integration of custom AI models in Azure ML.
    • You can now download the input metadata of an Azure ML synchronization from the Synchronization Results dialog box.

    Lineage Harvester (CLI and Edge)

    • When synchronizing a technical lineage via Edge, Collibra Data Lineage now returns the correct result message.
    • When ingesting Matillion data sources via Edge, the Collibra Data Lineage service instances can now process the "startTimestamp" parameter.

    October 6, 2024
    (collibra-edge-2024.07-91) 

    Security

    • We improved the security of integrations via Edge.

    Metadata integrations

    • For Dataplex Lineage , you can now download the metadata input file from the "Synchronization Results" dialog box.
    • For Dataplex Lineage, interactive queries that are run in GCP are no longer shown in the source code pane of the Technical Lineage Viewer.
    • The Databricks Unity Catalog Lineage integration now supports OAuth. When you create a connection to Databricks Unity Catalog via Edge, you can now select OAuth as the Authentication Type.

    September 30, 2024
    (data-lineage-2024.09.5) 

    Collibra Data Lineage Service

    • When ingesting SAP Analytics Cloud data sources, the Collibra Data Lineage service instances now successfully process the metadata, regardless of the order in which the SAP Analytics Cloud assets are returned by the SAP Datasphere API.
    • When ingesting Oracle data sources, Collibra Data Lineage now correctly sets the database and schema for packages, and correctly shows the package name.
    • When ingesting SAP Hana data sources, the Collibra Data Lineage service instances now support the use of the (+) operator in WHERE clauses.
    • When ingesting Snowflake data sources, the Collibra Data Lineage service instances now support:
      • SQL statements that contain a lot of Common Table Expressions.
      • SQL statements with a wildcard in the select list and indirect lineage that refers to the wildcard.

    September 29, 2024
    (collibra-edge-2024.07-84) 

    Security

    • We have improved the security of Edge, Catalog Data Classification, Technical Lineage for Databricks, Azure ML, Databricks Unity Catalog synchronization, ADLS Synchronization and SAP Datasphere.

    Protect

    • If a column is replaced by another column with the same masking and Protect groups (GCP principals), Protect for BigQuery now applies masking to the new column.

    Metadata integrations

    • JDBC Metadata Synchronization via Edge is now more stable. A retry mechanism was added to the data transfer to Data Intelligence Platform.
    • The Databricks Unity Catalog metadata integration now support OAuth. When you create a connection to Databricks Unity Catalog via Edge, you can now select OAuth as the Authentication Type. This authentication method is not supported for Databricks Unity Catalog Lineage from Edge 2024.07-91.
    • You can now use the AWS SageMaker AI capability if your Edge site is installed using one of the following types of forward proxy:
      • Path through (No authentication)
      • Path through (Basic authentication)
      • No proxy for noProxy hosts defined by Edge
    • Note The AWS SageMaker AI capability can't be used on an Edge site installed using a Man-in-the-middle (MITM) proxies.
    • You can now use the Azure ML capability if your Edge site is installed using one of the following types of forward proxy:
      • Path through (No authentication)
      • Path through (Basic authentication)
      • No proxy for noProxy hosts defined by Edge
      • Note The Azure ML capability can't be used on an Edge site installed using a Man-in-the-middle (MITM) proxies.
    • : You can now participate in a preview testing for the new Dataplex Catalog integration. In view of this beta, the "Ingestion Type" field is shown when you synchronize a Dataplex data source. If you are interested in using this new feature, do sign up for the beta to get access to the documentation, provide feedback, and get support.

    Lineage Harvester (CLI and Edge)

    • We fixed an issue with the CLI Harvester URI syntax on Windows.
    • When ingesting Netezza data sources via Edge, Collibra Data Lineage now correctly harvests views when multiple databases are specified in the capability.
    • When integrating Tableau Server data sources via Edge, Collibra Data Lineage now successfully harvests the default site, even if it was renamed in Tableau.

    September 27, 2024 Hotfix
    (data-lineage-2024.09.4.1) 

    Collibra Data Lineage Service

    • We made various small improvements to the overall performance and user experience.

    September 23, 2024
    (data-lineage-2024.09.4) 

    Collibra Data Lineage Service

    • We made several improvements for Oracle data source ingestion, which result in improved lineage extraction and faster processing. The improvements also establish a foundation for future enhancements, such as support for stored procedures and functions.
    • When ingesting BigQuery data sources, the Collibra Data Lineage service instances now support the use of the function ANY_VALUE in the PIVOT clause.
    • When integrating any of the supported BI or ETL data sources via Edge, theCollibra Data Lineage service instances now correctly analyze wildcards in embedded SQL statements.
    • When you ingest Snowflake data sources via the SQL-API mode, Collibra Data Lineage now delivers improved lineage results and fewer parsing errors due to metadata processing improvements.

    September 22, 2024
    (collibra-edge-2024.07-77) 

    Infrastructure

    • We fixed an issue where technical lineage capabilities that used the Shared Storage connection failed, due to a restrictive bucket quota.

    Metadata integrations

    • The SAP Datasphere integration now includes Column assets.

    September 16, 2024
    (data-lineage-2024.09.3) 

    Collibra Data Lineage Service

    • When ingesting MySQL data sources, the Collibra Data Lineage service instances now correctly construct schema names from the SQL statements.

    September 15, 2024
    (collibra-edge-2024.07-70) 

    Infrastructure

    • We fixed an issue where the Edge capability list was broken for customers who were using the Classic UI and had a deprecated DQ connector. With this fix, the capability list will display successfully in both the Classic and Latest UI, as expected.

    Security

    • We have improved the security of Edge and Classification.

    September 10, 2024 Hotfix
    (data-lineage-2024.09.2.1) 

    Collibra Data Lineage Service

    • Improved performance when integrating Power BI with DAX analysis enabled.

    September 9, 2024
    (data-lineage-2024.09.2) 

    Collibra Data Lineage Service

    • When ingesting BigQuery data sources, the Collibra Data Lineage service instances now support the use of "values" as an unpivot column name.
    • When ingesting Microsoft SQL Server data sources, the Collibra Data Lineage service instances now support:
      • EXECUTE statements with variables.
      • The OPTIMZE_FOR_SEQUENTIAL_KEY option in CREATE INDEX statements.
    • When ingesting JDBC data sources, the “Last sync time” column in the Technical lineage Sources tab page now shows the correct time, regardless of any parsing errors. Previously, if there were only parsing errors, the last sync time shown was incorrect.
    • When ingesting DataStage data sources, the Collibra Data Lineage service instances now update column names within file_item objects to capital letters.
    • When ingesting Snowflake lineage via SQL-API mode, the Collibra Data Lineage service instances no longer return a UNIQUE constraint failed error due to schema versioning.

    September 8, 2024
    (collibra-edge-2024.07-63) 

    Security

    • We have improved the security of data classification.

    Data Quality

    Lineage Harvester (CLI and Edge)

    • When integrating SAP Analytics Cloud, you can now configure container or folder filtering via the Data Catalog UI. For more information, go to Create a technical lineage via Edge.
    • When creating a technical lineage via the lineage harvester and providing passwords via the command line, you can now use “—passwords-stdin” with the “list-sources” and “ignore-source” commands. For more information on how to provide passwords, go to Technical lineage password manager integration design.

    September 1, 2024
    (collibra-edge-2024.07-56) 
    (data-lineage-2024.09.1) 

    Security

    • We have improved the security of Edge.

    Collibra Data Lineage Service

    • When ingesting JDBC data sources or creating custom technical lineage, Collibra Data Lineage more effectively diagnoses issues and provides you with improved logging and messaging.
    • When Snowflake lineage via SQL-API mode encounters multiple versions of a schema, lineage is processed and shown for the latest schema version. Previously, the processing of metadata batches that contained multiple versions of a schema failed and returned a "UNIQUE constraint failed" error.

    Lineage Harvester (CLI and Edge)

    • We made various small improvements to the overall performance and user experience of Collibra Data Lineage via Edge.

    August 24, 2024
    (collibra-edge-2024.07-48) 
    (data-lineage-2024.08.4) 

    Infrastructure

    • We have made improvements to the Edge installer to reduce future security vulnerabilities.

    Security

    • We have improved the security of Databricks Unity Catalog synchronization, Technical Lineage for Databricks Unity Catalog and Azure ML.

    Metadata integrations

    • The Databricks Unity Catalog integration no longer fails if tables are deleted in Databricks during the synchronization process.
    • We improved the security of integrations via Edge.

    Collibra Data Lineage Service

    • When ingesting Snowflake data sources, the Collibra Data Lineage service instances now support the CLUSTER BY clause in CREATE MATERIALIZED VIEW statements.
    • When ingesting DB2 data sources, the Collibra Data Lineage service instances now support the TABLE function.
    • In the Technical lineage Sources tab page, the Status description column now correctly renders the HTML formatting of the description text.

    August 18, 2024
    (collibra-edge-2024.07-42) 
    (data-lineage-2024.08.3) 

    Infrastructure

    • We improved the installation commands for Edge sites installed on:
      • Shared clusters via the Edge CLI method.
      • Dedicated or shared clusters via the Helm chart method.
    • Edge sites installed on bundled k3s from the 2024.07.42 release are on k8s 1.29. No action is required.

    Security

    • We have improved the security of Edge.

    Collibra Data Lineage Service

    • When integrating Tableau, with SAP HANA external data sources, for any SAP HANA tables that have names with “/” in them, the Tableau API response replaces “/“ by “::”. This resulted in missing stitching. The Collibra Data Lineage service instances now successfully accommodate this replacement in the API responses, so that stitching is now achieved.
    • When ingesting Redshift data sources:
      • Collibra Data Lineage service instances now support any order of the column constraint and column attributes.
      • Collibra Data Lineage service instances now support the QUALIFY clause.
    • When ingesting Snowflake data sources, the Collibra Data Lineage service instances:
      • Now support a trailing comma after the last column in the SELECT list.
      • Now successfully processes duplicate column names. Previously, duplicate column names resulted in missing lineage and analyze errors.
    • When ingesting Oracle data sources, the Collibra Data Lineage service instances now support BULK COLLECT INTO clause.

    August 11, 2024
    (collibra-edge-2024.07-35) 
    (data-lineage-2024.08.2) 

    Security

    • We have improved the security of Data classification via Edge.

    Metadata integrations

    • When integrating SAP Datasphere or SAP Analytics Cloud, SAP assets of types that are not supported by Collibra no longer cause the integration to fail. The presence of such assets now results in a warning.
    • Edge integration capabilities can now use a custom truststore when there is TLS termination at the firewall.
    • When you integrate Databricks Unity Catalog AI models, you can now choose to exclude all AI models in the 'system' Databricks catalog.

    Collibra Data Lineage Service

    • When ingesting Snowflake or Teradata data sources, SQL statements that include the “UNION ALL” operator no longer negatively impact performance, even when the resulting lineage is very large.
    • When integrating SAP Analytics Cloud, the integration no longer fails if, in SAP, a story or model is not included in a container. In the lineage in Collibra, the SAC Story and SAC Data Model will be grouped by a default SAC Container.
    • When you have open an SAC Story or SAC Data Attribute asset page, and you click on the Technical Lineage tab, the lineage graph for the relevant asset is now opened, as expected. Previously, the technical lineage viewer opened, but the relevant lineage was not shown.
    • When ingesting SAP HANA on-premises data sources, metadata processing no longer fails due to infinite recursion.
    • When ingesting DataStage data sources:
      • The Collibra Data Lineage service instances now correctly parse schemas and databases from connection URLs. Previously, some tables were incorrectly marked as being in DEFAULT databases or schemas.
      • Collibra Data Lineage no longer uses the database model from extension, as ingesting this model resulted in more analysis errors. We recommend that you use the shared database model feature to get the necessary table-definition details. This will help mitigate analysis errors, such as "Ambiguous column" and "please provide DDL".

    August 4, 2024
    (collibra-edge-2024.07-28) 
    (data-lineage-2024.08.1) 

    Infrastructure

    • Connections tests can now be completed successfully if the direct queries flag is enabled, as expected.

    Security

    • We have improved the security of Edge and Data classification via Edge.

    Data classification

    • You can now follow up on the results of a classification job by checking the Results dialog box. (idea #DCC-I-5694)
    • For numeric and date columns in Oracle, the sample data no longer shows the value "Invalid value" for all samples.

    Collibra Data Lineage Service

    • When integrating Power BI:
      • The correct URLs to paginated reports in Power BI are now shown on their respective Power BI Report asset pages.
      • Relations of the type "BI Data Model is source for / sources BI Data Model" are now created between:
        • Power BI Data Flow assets and Power BI Data Model assets.
        • Power BI Data Flow assets and Power BI Data Mart assets.
    • When ingesting Oracle data sources, the Collibra Data Lineage service instances now support the CONNECT BY clause.
    • When ingesting Snowfake data sources, the Collibra Data Lineage service instances now support all WITH options on the column level for CREATE TABLE and VIEW statements.

    Lineage Harvester (CLI and Edge)

    • We improved the performance of the BigQuery lineage capability.

    July 27, 2024
    (collibra-edge-2024.07-20) 
    (data-lineage-2024.07.5) 

    Security

    • We have improved the security of Edge.

    Metadata integrations

    • The technical lineage for Google Dataplex is now generally available. Via the Technical Lineage for Dataplex capability, you can ingest lineage from Google Dataplex Catalog into Collibra Catalog.

    Collibra Data Lineage Service

    • When ingesting Oracle data sources, the Collibra Data Lineage service instances now support XMLTable and JSON_TABLE with the AS operator.
    • When ingesting Spark data sources, the Collibra Data Lineage service instances now support multiple aliases defined as a tuple.
    • When ingesting Snowflake data sources, the Collibra Data Lineage service instances now supports the CONNECT BY clause.

    Lineage harvester (CLI and Edge)

    • The lineage on Edge job is correctly reported as failed now when it failed.
    • dbt Cloud lineage now supports longer accountID numbers. Previously, the dbt Cloud lineage processing could fail due to a change in the accountID data type in dbt Cloud, which was changed from int to bigint.

    July 25, 2024
    (data-lineage-2024.07.4.1) 

    Collibra Data Lineage Service

    • BI and ETL scanners via Edge and CLI Harvester no longer fail with the error "malformed \N character escape".
    • We fixed an internal whitespace processing issue for Snowflake data sources which resulted in Lineage missing from some temporary tables.

    July 21, 2024
    (collibra-edge-2024.07-14) 
    (data-lineage-2024.07.4) 

    Data classification

    • The Unified Data Classification process is now more stable when working with large datasets.

    Metadata integrations

    • The AWS SageMaker AI integration via Edge is now available in public preview. When you integrate Amazon SageMaker, you integrate the metadata of ML models from Amazon SageMaker AI to Collibra Data Intelligence Platform. The resulting assets represent the AWS SageMaker AI model.
    • The Azure ML integration via Edge is now available in public preview. When you integrate Azure AI, you integrate the metadata of ML models from Microsoft Azure ML to Collibra Data Intelligence Platform. The resulting assets represent the Azure ML model.

    Collibra Data Lineage Service

    • When ingesting DataStage data sources, the Collibra Data Lineage service instances now:
      • Correctly resolve parameters that are defined in the DSX file job, even if they aren't listed in the env file.
      • Correctly process ORCHESTRATE tables, which no longer result in "Ambiguous column" errors.
      • Correctly process Windows files. Additional backslashes “\” are no longer added to the file path.
    • When ingesting Informatica PowerCenter data sources, files are now correctly processed. Collibra Data Lineage no longer misinterprets them as tables. This allows for end-to-end lineage.
    • Collibra Data Lineage for Databricks now supports external delta tables referenced by external paths.

    July 14, 2024
    (collibra-edge-2024.07-7) 
    (data-lineage-2024.07.3) 

    Security

    • We have improved the security of Data classification.

    Collibra Data Lineage Service

    • We resolved a column position numbering issue when creating a Custom technical lineage, which was causing synchronization to fail.

    Lineage harvester (CLI and Edge)

    • When ingesting BigQuery data sources via Edge, you can now use the new “Billing ID” field in the Edge capability to specify a project ID for billing purposes. In this release, the “Billing ID” field is optional, but in a future version of Collibra, it will be mandatory. This new field works in conjunction with the “Project ID” field. For complete information, go to Create a technical lineage via Edge and review the “Billing ID” and “Project ID” field descriptions.
    • When ingesting DataStage data sources, the Collibra Data Lineage service instances can now process Sybase stages.

    July 7, 2024
    (collibra-edge-2024.07-0) 
    (data-lineage-2024.07.2) 

    Collibra Data Lineage Service

    • To mitigate "ambiguous column" errors, we improved the interoperability between the Power BI scanner and the SQL scanner on the Collibra Data Lineage service instances.
    • When ingesting Snowflake data sources, the Collibra Data Lineage service instances can now process "deferrable" as a column name.
    • When ingesting Teradata data sources, the Collibra Data Lineage service instances can now process “JSON_COMPOSE” and “JSON_PUBLISH” functions, arrays and double-dot access notations.
    • We fixed an issue where files that had "/" in the name caused the Lineage Harvester to fail.