Release 2023.09

Release 2023.08

Note The legacy documentation hosted at dq-docs.collibra.com has reached its end-of-life period and now has a redirect link to the official Collibra Data Quality & Observability documentation.

Release 2023.07

Note The legacy documentation hosted at dq-docs.collibra.com will reach its end-of-life alongside the upcoming August (2023.08) release of Collibra Data Quality & Observability.

Maintenance Updates

2023.07.2

• Fixed an issue where users who previously used the API integration on Collibra DQ version 2023.05 to import Collibra DQ metadata into Collibra Data Intelligence Cloud received an error message for Flyway scripts when migrating records from the integration status table to the integration history table after upgrading to Collibra DQ version 2023.07.
• Fixed an issue where preview data on the Findings page did not display fully when column values used scientific notation.

2023.07.4

• When using the integration API, the DQ Rule governs DQ Job relation of the DQ Rule asset no longer incorrectly identifies the "SOURCE" and "TARGET" properties in the integration JSON file.
• Fixed a critical CVE (CVE-2023-34034) in Collibra Data Quality & Observability version 2023.07 that was identified after the release date.

Release 2023.06

• Highlights
• Enhancements
• Fixes
• Known Limitations
• DQ Security Metrics
• MUI Redesign

Highlights

• When running rules against datasets that return many breaking records, you can now optionally export the records to an external Amazon S3 or Azure storage bucket instead of writing them to the PostgreSQL Metastore. By offloading break records to cloud storage, you have more control over how you manage the results of your DQ jobs, and you can store data in the supported remote connection of your choice.
• When building SQL rules to run against a dataset, you can now use the new Rule Workbench to create, edit, and preview SQL conditions to help verify that your data adheres to your organization's business requirements.

Enhancements

Capabilities

• You can now scan data stored in Trino using the Starburst Trino JDBC connection.
  • Ensure that your connection URL contains the following substring: &source=jdbc:presto. For example, jdbc:trino://example-host.trino.galaxy.starburst.io:443/sample?SSL=true&source=jdbc:presto
• When working with remote file connections, you can now leverage the Hudi Spark connector to scan Hudi files.

Note The Hudi Spark connector requires a separate package to work properly due to a security vulnerability in the Hudi bundle jar. Please reach out to your CSM for more information about accessing this package.

• When using the Estimate Job feature to gauge the resource requirements of a Spark job, you can now set partitionautocal to true on the Admin Limits settings page to automatically calculate Spark partitioning for optimal performance results.
• The Estimate Job feature now estimates the overall memory requirements instead of the memory per executor.
• You can now use the Data Class and Template Rules pages to manage out-of-the-box and custom Data Class and Template rules.
• The dayswithoutData and runswithoutData stat rules now count Day 0 and Run 0 as the first day and run without data.
• The dayswithoutData stat rule now counts days with stale data for 365 days instead of 100.
• When using Source to check a column for mismatched data, you can now select the Strict Source Downscoring option to include -validatevaluesthresholdstrictdownscore in your query during Source setup and base the downscore value on the number of cell mismatches found across all columns. When using this option, you must also assign a key column for source validation.
• When a large number of Dupes are found in a DQ job run, the getDataPreviewByObsType API now has improved performance and no longer times out.

Platform

• When adding a new dataset from a Google BigQuery connection, you can now successfully import, query, and identify EXTERNAL table types.
• To address the conflict of JAASConf secret deletion with DQ jobs having longer Spark launch times for Driver and Executor pods, we adjusted the DQ agent's clean-up routine. (ticket #109256)

Pushdown

• When configuring the settings of a Pushdown job, you can now choose to log all SQL queries for a dataset by turning SQL Logging on or off from the Settings modal.
• When reviewing the Value column for Outliers on the Findings page, low-precision values now truncate after 2 decimal places when all the trailing values are 0. For example, 3780.0000000 now truncates to 3780.00. High-precision values, such as 162.9583789, still display all decimal values.
• When adding ML layers for Databricks Pushdown jobs, you can now configure numerical outliers. Support for categorical outliers is planned for an upcoming release.
• Because Pushdown is not yet available for DQ Cloud, the Pushdown checkbox option on the Databricks and Snowflake connection templates is temporarily unavailable when setting up a connection on a DQ Cloud deployment.

DQ Cloud

• When admin or tenant admin users need to view the state of an Edge site identifier graph, you can now use the following APIs:
  • As admin
    • GET /v3/diagnostics/edgeSiteIdCache returns a text/plain body with a graph when successful.
    • DELETE /v3/diagnostics/edgeSiteIdCache returns no response body when successful.
• As tenant admin
  • GET /tenant/v3/diagnostics/edgeSiteIdCache/{tenant} returns a text/plain body with a graph when successful.
  • DELETE /tenant/v3/diagnostics/edgeSiteIdCache/{tenant} returns no response body when successful.

Note The tenant admin API works only for the {tenant} where the user is tenant admin.

Fixes

Capabilities

• When viewing Outlier records on the Findings page, you can again drill into individual records to view the associated graph. (ticket #110281)
• Rules with null characters in the data again return rule breaks. Previously, null characters caused rule break inserts into the Metastore to return exception messages. (ticket #103402)
• When exporting rule breaking records to Excel, integer values from Collibra DQ no longer display as decimal values in the Excel export file. (ticket #112830)
• Fixed an issue where Shapes detection incorrectly assigned non-numeric text as numeric scientific notation. (ticket #113704)

Platform

• When using an SSO configuration to sign into Collibra DQ, you no longer get errors when you attempt to sign in. The refactoring in this fix initially looks up a user profile by username, then by external user ID, before attempting to lookup by externalUserId until a user is found and returned. (ticket #109171)
• When drilling into a column on the Profile page, Min and Max string length again displays the correct values. (ticket #110044)
• When reviewing the Data Summary Report, the Table/File Name column now displays the correct name. (ticket #111508)
• Fixed the builds for the 2023.05 Collibra DQ version. Previously, jobs failed with an "Unknown" status during the Alerts activity and showed a "NoClassDefFoundError" in the job log. (ticket #115956, 116052)
• When running jobs on existing datasets with alerts configured, jobs no longer fail with an error when the ALERT_SCHEDULE_ENABLED option is set to TRUE. (ticket #112837)

DQ Cloud

• When drilling into rule break records on the Findings page, data preview records again display correctly. (ticket #114162)
• When reviewing the Completeness Report, data now displays correctly when you load the page and update as the inputs change. (ticket #115312)

Pushdown

• When using query wrapping in Snowflake Pushdown profiling, you can now successfully run a profile scan without errors. (ticket #111977)

Known Limitations

Capabilities

• When using BigQuery datasets and tables with names that begin with a number, there is a limitation that causes DQ jobs to fail.
  • A workaround is to wrap the dataset or table name with back quotes ` and then update the scope before you run the DQ job. For example, select * from `321_apples.example` and select * from `samples.311_service_requests`
• When using the Rule Template to build SQL rules, there is a limitation with SQLF type rules where an extra select clause is added into the query when:
  • SQL keywords, such as select, from, and where are not lowercase.
    • A workaround is to write all keywords in lowercase.
  • "@DATASET", "@dataset", and "DATASET" are used to reference a dataset.
    • Instead, use "dataset" in all lowercase letters without an "@" symbol.
• When exporting break records to external storage buckets, there is a limitation that prevents support for the feature on Amazon S3 and Azure connections that use SAML and Instance Profile authentication.
  • A workaround is to use Access Key authentication instead.
• When using the getRuleBreaksCreateTable API to create a table statement for break records exported to an external storage bucket, there is currently a limitation that prevents the return of the proper response. While this issue will be addressed in the 2023.07 release, this API is not intended to be used at this time.

Platform

• When leveraging the Spark 3.2.2 standalone installation that comes with the AWS marketplace installation, there is a limitation due to a jar mismatch for the AWS S3 Archive feature. The issue is that the existing hadoop-aws.3.2.1.jar file is incompatible with the feature.

  • A workaround is to update the hadoop-aws-3.2.1.jar to hadoop-aws-3.3.1.jar in the spark/jars directory. The necessary .jar file can be obtained from the following link: Apache Downloads.

    Note If you encounter any difficulties locating the necessary jar file on the Apache Downloads page, contact your CS or SE for assistance.

DQ Cloud

• DQ Cloud does not currently support SAML configuration.
• When reviewing the Completeness Report, new data only displays correctly after you upgrade your Collibra DQ Cloud instance to version 2023.05.2 or later.
• If an Edge site needs to be reinstalled, you must use the original PostgreSQL metastore database or metastore corruption may occur in Collibra DQ. If necessary, restore the metastore database from a backup before reinstalling. Ensure that the installation command line parameter collibra_edge.collibra.dq.metastoreUrl points to the correct database.

DQ Security Metrics

The following image shows a chart of Collibra DQ security vulnerabilities arranged by release version.

The following image shows a table of Collibra DQ security metrics arranged by release version.

MUI Redesign

The following table shows the status of the MUI redesign of Collibra DQ pages as of this release. Because the status of these pages only reflects Collibra DQ's internal test environment and completed engineering work, pages marked as "Done" are not necessarily available externally. Full availability of the new MUI pages is planned for an upcoming release.

Page	Location	Status
Homepage	Homepage	Done
Sidebar navigation	Sidebar navigation	Done
User Profile	User Profile	Done
List View	Views	Done
Assignments	Views	Done
Pulse View	Views	Done
Catalog by Column (Column Manager)	Catalog (Column Manager)	Done
Dataset Manager	Dataset Manager	Done
Alert Definition	Alerts	Done
Alert Notification	Alerts	Done
View Alerts	Alerts	Done
Jobs	Jobs	Done
Jobs Schedule	Jobs Schedule	Done
Rule Definitions	Rules	Done
Rule Summary	Rules	Done
Rule Templates	Rules	Done
Rule Workbench	Rules	In Progress
Data Classes	Rules	Done
Explorer	Explorer	In Progress
Reports	Reports	In Progress
Dataset Profile	Profile	In Progress
Dataset Findings	Findings	Done
Sign-in Page	Sign-in Page	Done

Release 2023.05

• Highlights
• New Features
• Enhancements
• Fixes
• Known Limitations
• DQ Security Metrics
• Maintenance Updates

Highlights

• We are excited to announce that Pushdown processing for Snowflake is now generally available! Pushdown is an alternative compute method for running DQ jobs, where Collibra DQ submits all of the job's processing directly to a SQL data warehouse, such as Snowflake. When all of your data resides in Snowflake, Pushdown reduces the amount of data transfer, eliminates egress latency, and removes the Spark compute requirement of a DQ Job.
• We are also excited to announce that Pushdown processing for Databricks is now available as a public beta! When you use Pushdown for Databricks ensure that PUSHDOWN_FOR_DATABRICKS is set to TRUE in the Application Configuration page of the Admin Console.
• You can now use Swagger to leverage the new Integration API to send Collibra DQ rules, ML layer findings, and associated data quality scores to Collibra Data Intelligence Cloud. With data quality details in Collibra Data Intelligence Cloud, you can develop a more robust understanding of the health and performance of your organization's data.

New Features

Capabilities

• When you create or edit a connection with REACT_MUI off, you can now define variables from the Connections template to securely enter sensitive properties, such as user credentials.
• When you enable Include Links for recent job runs, the email alert now includes multiple contextual links to help you access the affected areas of the application.

Platform

• You can now use a serverless agent to submit jobs from the UI. This lets you have a Collibra DQ installation without a native DQ agent, and allows for extensive agent customization and lightweight deployment options against new compute engines. This is currently only supported for Dataproc.

Pushdown

• You can now set the maxconcurrentjobs config on the Admin Limits page to specify a maximum number of concurrent Pushdown jobs to run at once to prevent the Job service from overloading.
• You can now use the new /v3/rules/{dataset}/validatePushdown endpoint to validate the syntax of Pushdown rules.

DQ Cloud

• You can now edit and delete DQ Cloud connections.
  • When you delete a connection all of the links to its agent are also deleted. When you create a new connection in DQ Cloud, ensure that in the connections template your Connection URL is unique and select an agent from the Target Agent dropdown menu. This step is required and you cannot change your agent after the connection is created.

Enhancements

Capabilities

• When you use a key comparison for source validation of decimal values that include scales of 0, you can now select a new Ignore Precision option from the Source configuration tab or set the flag, -validatevaluesignoreprecision, to true from the command line to ignore scales of 0 for integers before decimals and fractional values after decimals.

  Note -validatevaluesignoreprecision is only available for Validate Source when you include a key.

Platform

• The connection template is now updated to the correct Impala JDBC driver, com.cloudera.impala.jdbc.Driver
• The Kafka Streaming Connection is no longer available from the Connections Management page because it has finished its beta cycle and has not been promoted to becoming generally available.
• The reactor-core package now supports Spark245 for successful Azure connections.
• When you configure AdaptiveRules, Data Type Check is now included in the Schema detection activity.
• When you select the Include Links option on the Alerts Configuration page, you must also enter your host address from the URL of your application into the HOST_NAME input field on the Application Configuration page. For example, if your Collibra DQ URL is http://dq.collibra.com, you need to enter http://dq.collibra.com into the HOST_NAME input field.
  • The Include Links feature for alerts now has logging to show when the Include Links option is selected but HOST_NAME is not set.
    • Informational text is now available on the Alerts Configuration page to help with the configuration of alerts.

Pushdown

• When you run a Pushdown Job with Replay on, the start time of child Jobs in the Jobs queue now reflects their actual start times instead of the start time of the parent job from which the Replay initiated.
• The Outliers option of the Add Layers step is now disabled for Databricks Pushdown job configuration.

DQ Cloud

• DQ Cloud is now upgraded to the Collibra DQ 2023.05 version.

Fixes

Capabilities

• Fixed an issue with the email lookup query of password reset requests that prevented users from resetting passwords. (ticket #110075)
• Added a new admin limit flag, valsrcdisableaq, to fix a slow performance issue for record insertion into the assignment_q metastore table. (ticket #108547)
  • valsrcdisableaq lets you turn the connection between the assignmentQ feature and Source activity on or off. When you set it to true, you cannot invalidate or retrain any Source findings.
• Removed the scan button from Explorer Connections because it was no longer supported from the UI. You can still profile multiple tables at the same time with the /v3/datasetDefs/ or /v2/run-catalog-scan-json/ endpoint. (ticket #107687)
• Fixed an issue where, when DQ jobs were created from a BigQuery source and a Hive source was added, the suffix ‘/core’ was appended to the end of the driver name of the secondary dataset driver path, which resulted in long run times and an unavailable agent. (ticket #109796, #111432)
• Fixed an issue with where loading a CSV file that use Custom delimiters on S3 remote file connections caused the file to hang in the load activity. (ticket #108890)
• Fixed an issue with an incorrect mismatch in the validate source results, when both the source and target had values of zero. (ticket #106788)
• Fixed an issue where attempts to invalidate findings in bulk hung on the "Updating Dataset" message because of an unsupported request method. (ticket #106826, 113881)
• Fixed a permission issue on SQL Server Kerberos-based connections for queries run in Collibra DQ on system tables in SQL Server. (ticket #110773)

Platform

• Fixed issues where external users could not successfully run jobs. (ticket #110773, 111988, 112417, 112857)
• Fixed an issue with Collibra DQ on AWS Cloud where Instance Profile authentication caused scheduled S3 jobs to fail. (ticket #110570, 110574)
• Addressed all the vulnerabilities of the optional drivers from Collibra DQ version 2023.03. You can now take the images with the optional drivers, as they now pass security scans. (ticket #112617)

DQ Cloud

• Fixed an issue where scheduled jobs did not run because they became stuck in "Staged" status. (ticket #112802)

Known Limitations

Capabilities

• A limitation with S3 remote file connections that use an escape character as a delimiter causes columns to parse incorrectly. For example: /a
• When you edit an existing connection and its details, another connection is created and any sensitive properties from the old connection do not persist in the new connection.
  • A workaround is to recreate the sensitive properties from the old connection on the new connection.
• When you create or edit connections, the new sensitive properties feature is only available with React turned off.
  • This only works for datasets created before 2023.05. Permalinks to specific Job runs in alert emails only work for datasets that run after the introduction of this feature in Collibra DQ version 2023.05. If a dataset was created before this implementation and runs on a schedule, the permalinks will not work.
• Native SQL is not currently supported on the Rules Workbench.

Platform

• If you are an external user of Collibra DQ versions 2023.03, 2023.04, and their patches, you may experience issues where completed jobs do not send alerts. If this occurs, set ALERT_SCHEDULE_ENABLED=false and then restart web and agent.
• If a license key value is damaged or deleted in a current app session you may experience job failures with license key errors.
  • If you know that your deployment of Collibra DQ has a valid license key, you can attempt to refresh the page, sign out of the app and then sign back in. This will sync your license key with the metastore, which will allow you to once again run jobs without license key expiration job failures.

DQ Cloud

• Instance Profile is not supported for S3 connections.
• When using the Completeness Report, data only appears after upgrading to 2023.06 or later.
• When using the Findings page, you currently cannot drill into a rule break record. While there is no workaround for this limitation, a fix is planned for the 2023.06 release.
• When using the Findings page, you currently cannot tag job runs as off-peak. This will be fixed in the 2023.07 release.

Pushdown

• When scanning for dupes, fuzzy match duplicates display incorrectly as "NULL" values on the Findings page. This will be fixed in the 2023.06 release.

DQ Connector

• When navigating the Admin Console menu with React turned on, an "Integrations" option leads to a non-functional page. This will be fixed in the 2023.06 release.

DQ Security Metrics

The following image shows a chart of Collibra DQ security vulnerabilities arranged by release version.

The following image shows a table of Collibra DQ security metrics arranged by release version.

MUI Redesign

The following table shows the status of the MUI redesign of Collibra DQ pages as of this release. Because the status of these pages only reflects Collibra DQ's internal test environment and completed engineering work, pages marked as "Done" are not necessarily available externally. Full availability of the new MUI pages is planned for an upcoming release.

Page	Location	Status
Homepage	Homepage	Done
Sidebar navigation	Sidebar navigation	Done
User Profile	User Profile	Done
List View	Views	Done
Assignments	Views	Done
Pulse View	Views	Done
Catalog by Column (Column Manager)	Catalog (Column Manager)	Done
Dataset Manager	Dataset Manager	Done
Alert Definition	Alerts	Done
Alert Notification	Alerts	Done
View Alerts	Alerts	Done
Jobs	Jobs	Done
Jobs Schedule	Jobs Schedule	Done
Rule Definitions	Rules	Done
Rule Summary	Rules	Done
Rule Templates	Rules	Done
Rule Workbench	Rules	In Progress
Rule Builder	Rules	In Progress
Data Classes	Rules	Done
Explorer	Explorer	In Progress
Reports	Reports	In Progress
Dataset Profile	Profile	In Progress
Dataset Findings	Findings	Done
Sign-in Page	Sign-in Page	Done

Maintenance Updates

2023.05.1

• Fixed the builds for the 2023.05 Collibra DQ version. Previously, jobs failed with an "Unknown" status during the Alerts activity and showed a "NoClassDefFoundError" in the job log. (ticket #115956, 116052)

Release 2023.04

• Highlights
• New Features
• Enhancements
• Fixes
• Known Limitations
• DQ Security Metrics
• Maintenance Updates

Highlights

• We are excited to announce that Pushdown for Snowflake is now generally available! Pushdown is an alternative compute method for running a DQ Job, where Collibra DQ submits all of the Job's processing directly to a SQL data warehouse, such as Snowflake. When all of your data resides in Snowflake, Pushdown reduces the amount of data transfer, eliminates egress latency, and removes the Spark compute requirement of a DQ Job.
• Six new out-of-the-box reports are now available:
  • User Activity shows user click activity in Collibra DQ.
  • Row Count by Dataset shows the number of rows in a given dataset.
  • Alert Details shows alert details and the method by which they are sent, for example email.
  • Job Runs per User shows the number of Jobs run per user over a certain period of time.
  • Daily Job Runs per User shows the number of Jobs run per user on a particular day.
  • Rule Updates per User shows when a user-created rule is inserted, updated, or deleted, and applied to the dataset by a user over a certain period of time.

Note 
With the development of the newly designed Template Rules page in the upcoming the May release, we will use the newly built v2/createcustomrule API for custom rules and will deprecate the old v2/insertcustomrule.

Warning 
When you enable Include Links on the Alerts Configuration page of the Admin Console, you must also enter your host address in the HOST_NAME input field on the Application Configuration page. If the HOST_NAME input field does not contain a host address when Include Links is enabled, your DQ Jobs will fail.

New Features

Reports

• The User Activity, Row Count, Alert Details, Job Runs per User, Daily Job Runs per User, and Rule Updates per User reports are now available.

Enhancements

Rules

• You can now view rows scanned and rows breaking into the rule_output table.

Reports

• You can now view and filter reports on column dimensions with the Column Dimension Dashboard. This dashboard provides an overview of all columns, datasets, and business units, and provides insights about total current DQ Dimension scores, Dimension scores over time, and DQ scores (along with other metadata) for each column.
  • This dashboard is the first version and design adjustments are planned for a future release.
  • We also plan to redesign the Reports page in an upcoming release to better list all charts and dashboards and make it easier for you to know what we offer and potential use cases for the reports and dashboards.
  • Contact the Collibra DQ Product team or your CSM to learn more.

Platform

• In order to further enable Kubernetes-deploying users to more easily configure certain parameters upon deployment, the following variables are now available as owl-web-configmap properties:
  • SAML_MAX_AUTH_AGE
  • SAML_ENABLED
  • SAML_ENTITY_ID
  • CORS_ALLOWED_ORIGINS
  • SAML_ENTITY_BASEURL
• With the MUI turned on, the DQ Score Cards tab is now called Views.

Pushdown

• Record change observations are now included on the Findings page for Pushdown Jobs.
• The functionality of the v3/rules/{source}/copy API to work across Pull-Up and Pushdown datasets is now extended.
• You can now add a description of your dataset from the Review page before you create a Pushdown Job.

Fixes

Rules

• Fixed an issue with the Rule Builder that prevented rules from properly validating. (ticket #106100)
• Fixed an issue with the Rule Builder that prevented the selection of available columns and limited the ability to scroll through the list of options on the Primary Column dropdown list. (ticket #110276)
• Fixed an issue with the rule breaks table within the Breaks tab where sorting the table by the Rule Name column caused an error to throw. (ticket #105410)
• Fixed an issue where, when a rule had sub-select at the beginning of the WHERE clause, the rule displayed an Exception status when it ran. (ticket #109812)

Explorer

• Fixed an issue with the Transform option on Athena connections, the DATE() function was incorrectly included when the job was executed with an unlocked Run CMD. (ticket #105316)

Platform

• Fixed an issue where, while editing an existing job in Explorer, Collibra DQ became stuck in the loading stage. (ticket #105573)
• Fixed an issue that incorrectly allowed the creation of local users even with LOCAL_REGISTRATION_ENABLED set to false. (ticket #110325)
• Fixed an issue where a role-less user was able to access the Edit Rule modal from the Rule table on the Findings page. (ticket #104129)
• Fixed an issue where the install packages for Collibra DQ versions 2023.02 and 2023.03 did not contain the owlmanage.sh script. (ticket #110786)

Security

• Fixed a potential security issue where the introduction of a smart pre-admin approval message on the sign-in screen in the 2023.03 release version is now reverted to the previous sign-in error message.

APIs

• Fixed an issue the /v2/get-job-log API where the Job Log did not load and threw an error when more than two datasets were included in a rule. (ticket # 105498)

Connections

• Fixed an issue where too many open connections prevented new connections from being opened. (ticket #107034)
• Fixed an issue where a database connection remained idle and did not close when the /v2/getsqlresult API was called. (ticket #108365)

Source

• Fixed an issue where Redshift source queries failed when -profilePushdown count option was used. (ticket #106085)
• Fixed an issue with the Cell Threshold invalidation logic which caused the issue count to remain the same after the issue was invalidated and the job re-ran.

Known Limitations

Connections

• A limitation with Hive JDBC was observed where having both JDBC41 and JDBC42 drivers caused a conflict that prevents table data from loading. As a result, this release includes only the JDBC41 driver. This driver will be upgraded in a future release.
• Hive Direct job execution is currently not supported due to a technical issue that we plan to fix in an upcoming release.

Capabilities

• Sub-selecting columns of targets in the Source activity results in a failed Job when the Job runs.
  • A possible workaround is to keep the query as a select all (select *) operation.
• When you enable Include Links on the Alerts Configuration page of the Admin Console, you must also enter your host address in the HOST_NAME input field on the Application Configuration page.
  • A fix for this is planned for the May release.

Pushdown

• Pushdown is currently only available for on-premises deployments of Collibra DQ.
  • Support for Pushdown in DQ Cloud is planned for a future release.

DQ Connector

• There is an issue where Rest API calls from Collibra DGC to Collibra DQ result in a 403 Forbidden Error because Collibra DGC passes a cookie header which causes Collibra DQ to reject the request due to recent updates to CSRF token requirements. This limits Collibra DQ's ability to connect to Collibra Data Intelligence Cloud.
  • A possible workaround until a fix is available is to update export CSRF_TOKEN_ENABLED=false in the owl-env.sh file for Standalone deployments or update dq.security.csrf.token.enabled=${CSRF_TOKEN_ENABLED:false} in the Web ConfigMap for Kubernetes deployments.

DQ Security Metrics

The following image shows a chart of Collibra DQ security vulnerabilities arranged by release version.

The following image shows a table of Collibra DQ security metrics arranged by release version.

MUI Redesign

The following table shows the status of the MUI redesign of Collibra DQ pages as of this release. Because the status of these pages only reflects Collibra DQ's internal test environment and completed engineering work, pages marked as "Done" are not necessarily available externally. Full availability of the new MUI pages is planned for an upcoming release.

Page	Location	Status
Homepage	Homepage	Done
Sidebar navigation	Sidebar navigation	Done
User Profile	User Profile	Done
List View	Views	Done
Assignments	Views	Done
Pulse View	Views	Done
Catalog by Column (Column Manager)	Catalog (Column Manager)	Done
Dataset Manager	Dataset Manager	Done
Alert Definition	Alerts	Done
Alert Notification	Alerts	Done
View Alerts	Alerts	Done
Jobs	Jobs	Done
Jobs Schedule	Jobs Schedule	Done
Rule Definitions	Rules	Done
Rule Summary	Rules	Done
Rule Templates	Rules	In Progress
Rule Workbench	Rules	In Progress
Rule Builder	Rules	In Progress
Data Classes	Rules	To Do
Explorer	Explorer	In Progress
Reports	Reports	In Progress
Dataset Profile	Profile	In Progress
Dataset Findings	Findings	Done
Sign-in Page	Sign-in Page	Done

Maintenance updates

2023.04.1

• External users can now successfully run Jobs that include alert links.
  • The email address of the owner of a Job with alert links is no longer included in alert emails for both local and external users.

2023.04.2

• External users can now successfully run Jobs that include alert links.
  • The email address of the owner of a Job with alert links is no longer included in alert emails for both local and external users.
• Fixed an issue with Collibra DQ on AWS Cloud where Instance Profile authentication caused scheduled S3 Jobs to fail.