Only show release notes of Collibra Cloud for Government-certified features

Release 2023.03

Release information

  • Release date of Collibra 2023.03.0: March 5, 2023
    • Upgrade non-production environments: March 5, 2023
    • Upgrade production environments: March 26, 2023
  • Release date of Collibra 2023.03.1: March 12, 2023
  • Release date of Collibra 2023.03.2: March 26, 2023
  • Release date of Edge 2023.02.4: April 2, 2023
  • Release date of Edge 2023.02.5: April 23, 2023
  • Release date of Collibra 2023.03.3: On-demand only
  • Relevant Jobserver version: 2023.02.0-39

Highlights

  • We have moved the Collibra Data Lineage BI tool documentation files to a different directory on our servers. As a result, the URLs of the BI tool documentation topics have changed. For example, https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/<directory>/<file>.htm is now https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/<directory>/<file>.htm.
  • When you create technical lineage for IBM DataStage, CollibraData Lineage now parses the following:
    • The inner stage SQL statements, such as the INSERT and UPDATE statements, which are used to bind DataStage columns and target database objects in some stages.
    • Parameters that are passed by when a Job is called or used. The parameters are typically passed to the Job activity in a Sequence Job. Previously, CollibraData Lineage only parsed and created technical lineage for default parameters.
    • DataStage containers, including local and shared containers.
    • Runtime column propagation that is enabled on stages.
    • The account loop and stage variables of the Transformer stage.

Enhancements

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

  • When you integrate Power BI or Azure Data Factory (ADF integration is currently in beta), the lineage harvester now connects to the Microsoft cloud instance, instead of the login.microsoftonline.com host.
    Important This is only relevant for US government and national cloud Power BI customers.
  • When you integrate Tableau or Power BI, the nodes of any file data sources, for example Excel, CSV and Hyper files, are now more accurately identified as “file” nodes in the technical lineage Browse tab pane. Previously, they were identified as database nodes.
  • When you integrate Power BI, parameters are now ingested even if the “Enable load” option is not selected for the relevant parameters.
    Note To harvest columns and create a full technical lineage, the “Enable load” option must be selected. If it is not, the Power BI APIs will recognise parameterised tables, but not the columns in the tables. In which case, only table-level lineage is created; columns cannot be shown.
  • When you integrate Tableau, the lineage harvester now ingests parameters.
  • When ingesting Snowflake data sources via Edge, you can now choose between two ingestion methods:
    • SQL, to get lineage from view definitions.
    • SQL-API, to get lineage from view definitions and to get the vendor lineage from Snowflake.
  • You can use the new list-sources command to list all data sources that were ingested to create the technical lineage via the lineage harvester and technical lineage via Edge.
  • You can use the new ignore-source command to exclude a data source from the list of data sources to be used to create the technical lineage. To delete the technical lineage of a data source, you must remove the section of the data source from the lineage harvester configuration file and also run the ignore-source command.
  • You can export all analyzing and parsing errors by clicking the new Export Selected Transformations button on the technical lineage sources tab page.

Fixes

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

  • When you integrate Tableau:
    • And configure site filtering in your <source ID> configuration file, Tableau sites that are not mentioned in the filter are now correctly included in the ingestion. They are ingested in the default domain.
    • With a Google BigQuery data source, all BigQuery data objects now correctly appear in the technical lineage.
  • When ingesting MySQL data sources, the Collibra Data Lineage service instances now support the “as” keyword as optional in “create table” statements. Previously, parsing failed if the “as” keyword was missing. (tickets #105949, 106488)
  • After integrating Tableau via the lineage harvester, breadcrumbs on Tableau Data Attribute asset pages now accurately reflect the correct hierarchy of assets.
  • The URL attribute on Power BI asset pages now correctly shows the URL to GovCloud and Chinese tenants.
  • When you integrate SQL Server Reporting Services (SSRS) or Power BI Report Server (PBRS), folder filtering no longer fails when you want to ingest everything. (ticket #106126)
  • When ingesting Snowflake data sources, the correct source table is now shown in the technical lineagewhen the UNION operator is used. (ticket #107793)
  • Improved performance when analyzing batches from Microsoft SQL Server data sources, when queries contain variables. (ticket #106896, 109172)

Data Governance

  • You can once again create assets through Global create using domains with an inherited scope. (ticket #101853)
  • When you attempt to delete a relation type that is still used by a data quality rule, you will now get a clear error message to explain why the deletion fails.
  • You can no longer accidentally create duplicates by clicking the save button in the Add Complex Relations dialog multiple times as this button is now disabled after the first click.
  • You can once again add relations to assets of the Issue asset type and its subtypes through the 'Add Characteristic' dialog on an asset page. (ticket #98705).

Assessments

  • The translation files are now improved by fixing the fields that were not translated.
  • The following are now translated:
    • The Assessments text on the main menu
    • The description of the checkbox on the Assessments landing page

    (ticket #101774)

Miscellaneous

  • On the Homepage editor, the URL field on the Add a Quick Link card now accepts a complex link, for example, https://productresources.collibra.com/docs/collibra/latest/Content/DGCSettings/ServicesConfiguration/to_services-configuration.htm.

Collibra maintenance updates

Collibra 2023.03.1

Collibra 2023.03.2

  • You once again see asset recommendations on the Homepage and Data Marketplace.
  • You can use again a JSESSIONID cookie to authenticate API calls. (ticket #109761, 109775, 109976, 110042, 110363, 110592, 110729, 110798)
  • After an upgrade, environments with a large number of workflows that were started using the older version of the workflow engine no longer take a long time to restart.

Collibra 2023.03.3

  • When adding attributes from a table, the articulation score gets updated correctly again. (ticket #104955)

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.

Edge 2023.02.4

Catalog S3 Synchronization capability update 1

Edge 2023.02.5

Collibra Data Lineage capability update

  • Collibra Data Lineage now supports proxy servers for technical lineage via Edge. If a proxy setting is defined for the Edge site, it is automatically taken into account. Proxy server authentication is now supported. Custom SSL certificates are not yet supported. See Configure a forward proxy.