Release 2022.05

• Release information
• Highlights
• New features
• Enhancements
• Fixes
• Hotfixes

Release information

• Release date of 2022.05.0: May 8, 2022
  • Upgrade non-production environments: May 8, 2022
  • Upgrade production environments: May 29, 2022
• Release date of 2022.05.1
  • Upgrade non-production environments: May 22, 2022
  • Upgrade production environments: May 29, 2022
• Release date of 2022.05.2: June 5, 2022
• Release date of 2022.05.3: June 24, 2022
• Relevant Jobserver version: 2022.05.1-67

Highlights

• You can now use a browser extension to easily access Collibra data anywhere. Special experience foreseen for Tableau or PowerBI Dashboard metadata.

• Collibra Data Lineage now supports the following BI integrations:
  • MicroStrategy
  • SQL Server Reporting Services and Power BI Report Server
• You can now integrate Power BI in Data Catalog via the lineage harvester, meaning you no longer need to use the Power BI harvester. Additional benefits include the following:
  • Support for Power BI Data Flows.
  • Descriptions of Power BI Reports.
  • Statuses of Power BI Workspaces.
  • Filtering and domain mapping.
  Note The new Power BI integration method is specifically for new integrations. For those who have been ingesting Power BI via the Power BI harvester, we will soon release a migration script.

• The REST Import API v2 now supports importing responsibilities for communities, domains and assets.
• Azul Zulu JRE (Java Runtime Environment) is updated to version 11.0.14.1.

New features

Data Catalog

• A new REST API, REST Catalog Database Registration API, is available.
  This API allows you to register data sources via Edge and synchronize the metadata of these data sources outside of the UI.

Search

• When you rebuild the search index for your Collibra environment, the Output Module is now used to fetch the data. This new, default method greatly improves performance during index runtime. There are no changes to the search index configuration settings or the means by which you reindex your environment. If considered necessary, you can roll back to the old indexing method, via Collibra Console.

Enhancements

Data Catalog

• The percentage shown in the main menu Activities list now shows the actual progress of the activity for a Database Profiling via Edge job.

Data Lineage and BI integrations

• You can now use token-based authentication when creating a technical lineage for Matillion.
  
  Warning This enhancement is not backwards compatible.
  

  • You must update your lineage harvester configuration file.
  • If you use the lineage harvester 2022.05, you can no longer use the pwd.conf file with an older harvester.
• You can now use the lineage harvester and a new migration script, to migrate your Tableau assets to the new Tableau operating model.
• The State attribute type is now part of the global assignment of the Power BI Workspace asset type.
• The new Power BI Data Flow asset type now accommodates the ingestion of Power BI dataflows.
• The asset types Power BI KPI and Power BI Parameter are removed. SQL Server Reporting Services and Power BI Report Server now use the same asset types.
• If using a Tableau <source ID> configuration file:
  • You can now use wildcards throughout the file.
  • The hostName and connectorUrl properties are no longer case-sensitive.
• Looker Dashboard asset pages now include a URL to the dashboard in Looker, as a clickable link.
• If you set the useCollibraSystemName property to "true" in your lineage harvester configuration file, but don't define the system name in the Tableau <source ID> configuration file, the system name in the Tableau technical lineage now shows DEFAULT as the system name.
• When integrating Informatica Intelligent Cloud Services, Collibra Data Lineage now shows more meaningful error messages when taskflows cannot be processed. For more information and troubleshooting suggestions, see error codes MSG-LIN-19001 and MSG-LIN-19002 in the Documentation Center.
• The Collibra Data Lineage servers now assign names to SQL queries that are identified by BI and ETL scanners.
• lineage harvester 2022.05 includes an internal format change to the password manager pwd.conf file.
  
  Warning This means that if you use the lineage harvester 2022.05, you can no longer use the pwd.conf file with an older harvester.

Data Governance

• All user selection fields in dialog boxes and tables now show the users' first name, the last name and email address.
• Searching for users in user selection fields now also shows corresponding email addresses.
• Searching for users in user selection fields now also show email addresses next to the first and last name so that users with the same first and last name can be distinguished.
• If you import a CMA file using the Migration feature, you now see an overview of the changes before the actual import.

Collibra Console

• You no longer have to restart Collibra after changing the hyperlinking configuration.
• You can now enable or disable the ability to import responsibilities at asset level via the Import API with a new option in the Import configuration section. This option is disabled by default to ensure minimum impact on system performance.

Security

• If you try to reset your password but you enter a password that is too weak or the password confirmation is wrong, the fields are now cleared.
• You can now configure how long the link that is sent when you reset a password remains valid. The link that is sent when you request a password reset now becomes invalid if you request a new password reset. By default this time is set to 1h with a possible maximum of 24h.
• The default password policy for new environments now requires strong passwords. For existing environments, we recommend to review the password policy configuration.
• You can now configure a period during which you cannot sign in after entering a wrong password too many times. By default, new environments only allow for 3 attempts before a time delay of 5 minutes is triggered.

API

• The REST Import API v2 now supports importing responsibilities for communities, domains and assets.
• In the GET /assets REST API method, the statusId argument is deprecated, use the argument statusIds from now on.
• Additional capability metrics are added to the Edge GraphQL API which allow you to verify if capabilities are used, correctly functioning or failing regularly.

Miscellaneous

• Signing in via LDAP is now faster. (ticket #79896, 83727)
• The performance of bulk deleting assets with complex relations has improved.

Fixes

Data Catalog

• The Target Domain drop-down list now always shows up to 100 applicable target domains. To narrow the selection, you can start typing the name of the domain. (ticket #81360)
• To avoid out-of-memory issues, you can now use the 'Data set threshold' setting to limit the number of elements used in the Data Set recommender model training. (ticket #77440, 79644)
• Fixed an issue in Jobserver Job management that could prevent a job from completing. (ticket #83630)

Data Lineage and BI integrations

• Harvesting Tableau metadata via a proxy server no longer results in a TCP connection timeout error. (tickets #84759, 85620)
• Fixed an issue in the technical lineage viewer that resulted in an HTTP 410 Gone error.
• The lineage harvester no longer hangs when harvesting metadata from certain data sources.
• The Apache Hive JDBC driver is now upgraded from 2.6.17.1020 to 2.6.19.2022.
• The PostgreSQL JDBC driver is now upgraded from 42.3.2 to 42.3.3.
• If a Power BI dataflow specification does not contain entities, the attempt to process entities is skipped. (ticket #70082)
• When harvesting BigQuery metadata, materialized views are now harvested. (ticket # 84273)
• Fixed an issue in the Power BI harvester that caused an expired token error.
• Collibra Data Lineage now correctly traces to the underlying table when processing SELECT INTO statements targeted at a view.
• When harvesting IBM InfoSphere DataStage data sources, all inside SQL statements are now analyzed.
• The Collibra Data Lineage servers now benefit from several parsing enhancements when integrating BigQuery data sources, including support for the construct (replace * modifier ).
• Quoted identifiers in Microsoft SQL Server dialect are no longer case-sensitive. (ticket #85021)
• The Collibra Data Lineage servers now benefit from the following parsing enhancements when integrating Teradata data sources (ticket #84666):
  • Support for CREATE RECURSIVE VIEW.
  • Support for the DECLARE CURSOR statement in its dynamic SQL form.
  • PIVOT can be a table alias, even if it is a reserved keyword.
  • Improved support for SUBSTR/SUBSTRING function, to allow undocumented but supported variants.
  • Support for MINUS ALL and plain MINUS.
  • Support for INCLUDE_NULLS in TD_UNPIVOT as optional.
  • Support for CAST to TIMESTAMP WITH TIME ZONE AT.
• The lineage harvester automatically refreshes Tableau tokens. (tickets #82323, 85617)
• You can now use the optional concurrencyLevel property in the lineage harvester configuration file, to specify the internal sizing, meaning the amount of tasks that can be executed at the same time. (tickets #82323, 85617)
• When ingesting Tableau, automatic stitching is again creating the relation type "Data Element sources / targets Data Element" between Tableau Data Attribute assets and BigQuery Column assets. (ticket #86149)
• Fixed an issue in the technical lineage viewer that resulted in an HTTP 410 Gone error.
• Fixed a lineage harvester issue that was slowing the ingestion of columns. (tickets #84796, 84923)
• Fixed an issue in the merging algorithm that combines data from multiple data sources, which was causing unintended behavior in the Technical lineage viewer. (tickets #84780, 84925)
• Fixed an issue when synchronizing Tableau that resulted in the error message "A mapping for the external system id and resource already exists". (tickets #82323, 85018, 85132)

Data Governance

• Exporting assets with identical display names no longer causes a discrepancy in the number of exported assets under certain conditions. (ticket #78745, 83349)
• In the basic filter pane of an asset table, you can again see the asset type in the Properties section if filtering on asset type would only return one result.
• Using the touchpad to scroll horizontally in a table no longer causes your browser to return to the previous page.
• The scope icon no longer shrinks when the screen width changes or the left side of the screen is minimized.
• The community hierarchy immediately shows domains that are added in subcommunities.
• The community overview table no longer disappears when you create a new community that is not part of the current community.
• You can again select asset types within a subcommunity when you create an advanced filter. (ticket #80756)
• Editing the community name on a community overview page is now immediately in the table.
• In the Add assignment window, scopes are now listed in alphabetical order.
• Fixed a layout issue with the radio buttons and scope names in the Add assignment window.
• Collibra no longer stops responding when adding a boolean attribute during the creation of a complex relation type.
• In the tables of the Operating model, cell changes can no longer be saved with no value or with spaces only. In these situations, the Save button is disabled.
• The attachments page with a saved sorting order by date now correctly sorts the attachments when opening the page. (ticket #83219)
• A 'Save for all users' option for complex relation tables is now shown only to the users with the right permission. (ticket #81238)
• The domain type of the out-of-the-box 'Data Quality Dimensions' domain is now changed to Governance Asset Domain so you can create Data Quality Dimension assets in that domain. Note that this change is only done if you haven't edited the assignment of the Data Quality Dimension asset type. (ticket #75133)
• The Move Assets dialog box now closes correctly after moving assets from a table view. (ticket #85470)

Diagrams

• You can again start a new diagram from a node. (ticket #77428)
• When saving an edited diagram, the diagram view is overwritten instead of saving a new diagram view.

Search

• The quick search on the References tab is no longer case-sensitive. The search criteria don’t only involve full expression but also parts of it.

Collibra for Mobile

• You can again start workflows in Collibra for Mobile.
• On Android, the keyboard no longer disappears when trying to add text in text fields. (ticket #87239)

Security

• If you enter a wrong password too many times, your password status is set to inactive instead of your user account being disabled. An administrator will have to reset your password.
• A CSRF token is no longer missing from the response when no cookies are set for the auth/session API. (ticket #83781, 83808, 83822, 83862, 83892, 83920, 84009, 84054, 84164, 84182, 84455, 84767, 85028)
• If you change the email address of a user, Collibra now sends a notification via email to the old email address.

API

• You can no longer create a scope overlap via a GraphQL call.

Hotfixes

Collibra 2022.05.1

• Jobserver now anonymizes data correctly even if you changed the data type of more than one column with the same name in a schema. (ticket #87006). A new Jobserver version is available, version 2022.05.1-67.
• Fixed an issue where the upgrade stopped because custom characteristics are added to the 'Power BI Server', 'Power BI KPI', or 'Power BI Parameter' asset type in the environment.
• Fixed an issue where the upgrade could fail when reading a translation file that contains non UTF-8 characters.

Collibra 2022.05.2

• You no longer get a DataFetchingException error if historical guest users exist in the database and you open the Users page. (ticket #87959, 88857)

Collibra 2022.05.3

• Scheduled jobs for synchronizing, profiling and classifying a data source or Amazon S3 no longer fail and prevent the DGC service to start. (ticket #88808, 89602, 89938)
• You can now create and edit complex relations in fewer steps.

Lineage harvester hotfix 1

• Technical lineage Edge capabilities now run without having to set the QueryPassthrough parameter to “true” at the connection level.
• The lineage harvester on Edge now logs all errors from the load source phase.

Edge capability hotfix 1

• When you specify an invalid region name in the AWS region restriction console configuration, an error is now reflected in the logs.
• At the start of an S3 synchronization process, the search for previous AWS Glue databases now respects the AWS region restriction rules.