• Announcement
• New and improved
• Fixes

Release information

• Expected release date of Data Quality & Observability Classic 2026.06: July 6, 2026
• Release notes publication date: June 30, 2026

Announcement

New and improved

Platform

• You can now view Collibra Platform version information in log messages when starting the integration import processes. Spark Standalone customers must replace their log4j2.xml file with the updated version included in this release. No action is required for Kubernetes-based deployments.

Dataset Manager

• You can now automatically trigger a global webhook alert when a new dataset is created.

• The Dataset Overview now correctly shows null column values as "null" instead of blank cells. This improvement ensures that null values are distinguishable from empty rows, providing a more accurate representation of your data in the results table.

Admin configuration

• You can now use the new "RULE_CONDITION_DISPLAY" feature flag in Configuration Settings. When set to ON, the Rules tab and exported XLSX files show ruleCondition instead of ruleValue for pushdown and pullup datasets. By default, the flag is set to OFF, maintaining the current behavior.

Security

• We improved the security of our Java libraries.

Connections

• Databricks and Dremio drivers have been upgraded to the latest major versions to ensure continued compatibility and performance. The Databricks driver is now version 3.4.1, and the Dremio driver is now version 26.0.5-202509091642240013-f5051a07.

• The CDATA Bigquery JDBC driver has been updated to version 25.0.9539.0.

Fixes

Jobs

• You can now change the job size in the Job Estimator when the Default Master Path for k8s:// contains the word “local”.

• The "Driver Memory" field now updates immediately based on the job estimation result. The value is automatically calculated as half of the "Executor Memory" value, with a minimum of 2 GB, ensuring accurate and timely updates.

• Jobs no longer hang when canceled during the initialization (INIT) stage, allowing other jobs to start without requiring a service restart.

Alerts

• Data Quality alerts with configuration errors no longer prevent other alerts from firing. If an alert encounters an error during processing, it is now skipped and logged, allowing remaining valid alerts to trigger successfully.

• Webhook alerts now properly encode URLs in JSON payloads, ensuring complete URL generation including timestamps for findings_url variables.

Dataset Manager

• You can now copy and download query results from the Dataset Overview modal when dataset preview security is disabled, regardless of your user role.

• You can now see an accurate "Active" count that reflects the current dataset definition, even after switching between Add Layers and Review. Navigating to the Review page no longer locks the dataset configuration, allowing you to save additional edits. Added or deleted layers, such as Outliers and Shapes, now remain consistent across all screens until you modify them.

• Dataset audit logs now correctly show DATASET_SETTINGS instead of SHAPE_SETTINGS when you change dataset settings via the Explorer, providing more accurate information about the actual changes made.

Admin configuration

• You can now save ServiceNow assignment queue configurations without setting the "Publish only" option to true. Previously, the system incorrectly required this setting before allowing a successful save.

• You no longer experience premature logouts after 15–20 minutes of inactivity when using local user authentication in Data Quality. Sessions now properly respect the configured 1-hour timeout setting. Local user authentication (non-SSO) is no longer affected by this behavior.

APIs

• The v3/alerts API now validates that webhook alerts cannot be assigned a batch name, preventing invalid configurations and ensuring webhook recipients do not incorrectly appear in email batch selectors.

• When you create a rule using the POST /v3/rules API endpoint, the dimension name now appears correctly in the response instead of showing as null.

• Announcement
• New and improved
• Fixes
• Patch release

Release information

• Release date of Data Quality & Observability Classic 2026.05: June 1, 2026
• Release notes publication date: May 25, 2026

Announcement

New and improved

Platform

• You can now configure a custom Spark executor pod template for Livy by setting global.configMap.data.sparkPodTemplate in your Helm values. When provided, the template is automatically mounted into the Livy deployment and applied to all Livy Session executor pods.
• Data Quality & Observability Classic now supports EDB Postgres Advanced Server 15.x. This ensures compatibility with the latest certified version of the database.
• All necessary environments now have equivalent Helm variables. This ensures consistency and simplifies configuration management across environments.
• The Redshift JDBC driver is now upgraded to version 2.2.6.
• We improved the security of our Java libraries.

Jobs

• The Data Quality export functionality now handles large datasets with duplicate detection results more efficiently. The optimized process reduces API calls from thousands to one by using the batch endpoint, ensuring exports complete successfully. If an error occurs, user-friendly messages are now shown to assist with troubleshooting.
• Auto job resource estimation for jobs now allocates sufficient resources during job execution. This ensures that resource allocation matches the dataset size for each run, even if the dataset size changes.

Collibra Platform integration

• When an integration job fails, the integration console now shows an exception message for the failing data set. You can hover over the message to view the full details, making it easier to troubleshoot job failures.
• You can now use the "Transfer List" component in the Integration Automap UI to view, search, and select multiple tables efficiently. This feature allows you to search tables by name, filter results accurately, and move one or multiple tables between available and selected lists without duplication.

Fixes

Platform

• After logging in, you are now redirected directly to the intended resource, such as the Dataset Profile page or the Findings page. Previously, you were redirected to the Home page and had to click the link again to reach your destination.

• As part of the integration process between Data Quality & Observability Classic and the Collibra Platform, inactive data quality rules now correctly show as "Suppressed" in the Collibra Platform.

Jobs

• S3 jobs and Livy sessions using AssumeRole or Pod Identity no longer time out on "getFileStatus" after upgrading to Data Quality & Observability Classic 2026.03. Data Quality & Observability Classic now propagates the configured S3 region to Spark jobs and Livy sessions, resolving issues caused by cross-region access in environments with private S3 endpoints.
• The dataset source query compilation error in BigQuery Pushdown jobs after upgrading to Data Quality & Observability Classic 2026.03 has been resolved. The issue, caused by incorrect schema and table name parsing, is now fixed.
• The Metadata bar now correctly displays the schema and table name extracted from complex dataset source queries. This ensures accurate metadata representation for improved clarity and usability.
• Jobs no longer fail with a "value out of range: overflow" error when string or text values are processed as numeric. Statistical aggregations now exclude min, max, and mean absolute values exceeding 1.0e150, preventing PostgreSQL avg and stddev calculations from overflowing. Legitimately large numbers above this threshold are excluded, but infinity values are still preserved.

Findings

• The Export Limit configuration now enforces limits on CSV downloads and signed links for Pullup job archives. The "Download CSV" button generates files that adhere to the configured export limit, excluding the header row. Similarly, the "Copy Signed Link" action ensures the downloadable file does not exceed the export limit.
• The "Copy Signed Link" and "Download CSV" actions now honor the export_limit = 0 configuration. When this setting is applied, these actions are disabled, ensuring no records are exported.

Rules

• The "Data Class Actions" menu no longer disables the UI when you don't select "Edit" or "Delete." You can now close the drop-down by clicking outside of it, ensuring the screen remains interactive.
• Pullup rules now correctly identify break records when you use the equals (=) operator on columns with comma-separated values.

Dataset Manager

• Deleting or renaming a dataset with a common suffix now resolves only the intended dataset. For example, actions on "test_dataset" no longer affect "another_test_dataset."

Collibra Platform integration

• Custom rule statuses in Data Quality & Observability Classic now update to "NA" in the Collibra Platform when a rule moves to an exception state during integration. Once the exception is resolved, the status automatically reverts to "Passing" or "Breaking” in the Collibra Platform. While in the "NA" status, the rule's score is excluded from the Quality tab for that day, improving the handling of rules with exceptions.
• The "Passing Fraction" for the Outlier finding in the Collibra Platform now correctly reflects the corresponding outlier score from Data Quality & Observability Classic. For example, if the outlier score is 70, the "Passing Fraction" is calculated as 30 (100 − 70).

Patch release

2026.05.2

• We improved the security of the application.

2026.05.1

• Email notifications sent via the Microsoft Graph API now render correctly as HTML instead of displaying raw HTML source code in your email client.
• Scheduled Pushdown jobs on Snowflake data sources no longer fail with the "Unable to count rows for dataset" error that previously occurred sporadically.
• FIPS deployment no longer fails during password encryption initialization when using Bouncy Castle.

• New and improved
• Fixes
• Patch release

Release information

• Release date of Data Quality & Observability Classic 2026.04: May 1, 2026
• Release notes publication date: April 16, 2026

New and improved

Platform

• You can now configure access to scorecards and reports using the "Require INSIGHTS_VIEWER role to view scorecards and reports" setting in Security Settings > General. When enabled, only users with the ROLE_INSIGHTS_VIEWER role can access scorecards and reports, including sub-pages, ensuring stricter access control. Users without the role are redirected to the Access Denied page when attempting to access restricted content.
• You can now manage the WASBS storage account key securely through Azure Key Vault (AKV). This eliminates the need to store the key directly in the Helm values file, enhancing security.
• We upgraded the Databricks driver version to 2.8.0.
• Databricks Pushdown is now ANSI-compliant.
• We upgraded the OWASP ESAPI (Enterprise Security API) library to enhance application security and address known vulnerabilities. While no functional changes are expected, edge cases may behave differently.
• Data Quality & Observability Classic now supports the SQL Assistant for Data Quality feature when you have a Data Quality & Observability Classic to Collibra Platform OAuth-based integration. Previously, this capability was available only with Basic Authentication. This enhancement ensures broader integration options for leveraging SQL Assistant for Data Quality.
• You can now propagate labels and annotations to the Kubernetes metastore secret created by the DQ Agent service at runtime. This is configurable via Helm chart values, allowing you to customize the secret used by Pullup jobs.
• You can now customize the Kubernetes pod template for Spark driver and executor pods launched by the DQ Agent.
• You can now enable the PUSH_NA_TO_DIP application configuration setting to push adaptive rules with "Not Applicable" status to Collibra Platform. This setting is disabled by default and can be enabled in the Admin Console when the “Create Metric Assets” option is set to true in the integration configuration.
• You can now grant non-admin users access to the Admin > Integrations page based on their existing connection role mappings. When you enable the new "Enable Integration Management for Connection Users" setting in Security Settings, users with roles mapped to specific connections can view and configure integration settings for only those connections they have access to.
• You can now manage standardized tags using the new "Strict Tagging" feature. This feature ensures consistent metadata application by allowing users to select only approved tags from a dropdown. Admins can manage tags directly in the Admin Console under "Metatags," with validation to prevent duplicates and empty values. Additionally, new API endpoints are available for creating, updating, and deleting tags.
  • As a one-time conversion process, the values in the t1, t2, t3, and t4 columns of the owl_catalog table will be used to populate the new defined_tags table, with each unique value stored as a tag and assigned a unique identifier.

Jobs

• Databricks Pushdown jobs now run successfully on tables with special characters in column names.
• You now have more control over what sample and profiling data is stored in the metastore, helping you meet sensitive-data compliance requirements. In DQ Job Settings > Profile, you can switch Preview from Source independently of Archive Break Records, enabling sample data previews without storing them. A new Descriptive Statistics switch (default ON) allows you to exclude sensitive statistics, such as min/max values, from the metastore. Additionally, when Archive Break Records > Preview from Source is ON, rule query results are shown instead of full table records, and no break records are stored. For stricter data residency, set previewlimit to 0 and turn Descriptive Statistics OFF.
• Jobs now support the -metadataEnhancedBreakRecords command-line option. This allows archived break records to include additional metadata columns, providing more detailed insights.
• You can now enable metadata-enhanced break records for Pullup jobs. This option allows you to include additional data in pullup break records, aiding in remediation and reporting.
• The replay functionality no longer executes unnecessary SQL queries when you select "REPLAY" from the Run dropdown menu. This improvement significantly reduces wait times when working with complex SQL queries, as the system now only updates the timeframe without re-running the underlying query logic.

Findings

• You can now control user access to export functionality on the Findings page "Export" tab through role-based permissions. When the "Require DATA_EXPORT role to export rule breaks" security setting is enabled, users without the DATA_EXPORT role cannot access export checkboxes or buttons, while users with the role retain full export capabilities.

Rules

• You can now control export permissions for the "Copy Results" and "Download Results" buttons in Rule Workbench's Result Preview section. When the "Require DATA_EXPORT role to export rule breaks" setting is enabled, users without the DATA_EXPORT role will see these buttons disabled with a tooltip explaining they don't have permission to copy or download data.
• You can now configure the Purpose field as mandatory for custom rules to meet integration requirements. When the "MANDATORY_RULE_PURPOSE" configuration flag is enabled, the Purpose field is required for all rule types in Rule Workbench. The "Save" and "Submit" buttons are disabled until you enter a purpose.
• You can now add metadata columns to archived rule break records in Pullup jobs.

Alerts

• Email alerts now use 6-digit hexadecimal color codes to ensure the "Job Status" field displays correctly across all email clients.

Dataset Manager

• The "Copy to Clipboard" and "Download Results" options now respect the global exportlimit configuration setting, ensuring data extraction controls are uniformly enforced while maintaining full visibility of preview data on screen.

Collibra Platform integration

• The Data Quality & Observability Classic and Collibra Platform integration now uses a dedicated thread pool to increase integration job throughput without affecting other scheduler tasks. New properties provide granular control over job concurrency and thread queuing. For most customers, no changes are needed. However, if integration job throughput exceeds 50 jobs per hour, you may need to adjust the following properties:
  • dq.dgc.integration.job.thread.pool.size: Maximum concurrent jobs based on available threads (default: 10).
  • dq.dgc.integration.job.thread.pool.queue.capacity: Threads (jobs) concurrent + queued for the pool (default: 256).
  • dq.dgc.max.concurrent.integration.job: Batch size for integration jobs (default: 10).
• The metastore mapping table for integrating Data Quality & Observability Classic with Collibra Platform now includes a new column that shows the time stamp of when the table was mapped. This time stamp is added when you use the auto-map feature for a schema.
• You can now delete all mapping records at the schema level by selecting "Delete Mapping" from the three-dot menu. This action removes existing mappings for a specific schema, allowing you to clear outdated mappings before running the auto-map job. The delete mapping option works alongside the existing auto-map feature to help you maintain accurate schema-level mappings.
• When you delete a dataset from Data Quality & Observability Classic, the system now automatically removes the corresponding integration assets (job asset, score domain, and rules domain) from Collibra Platforminstances when the Application configuration property, ENABLE_DELETE_INTEGRATION, is set to true. This eliminates the need to manually identify and delete orphaned assets, reducing cleanup time and potential errors.
• You can now control which assets are created during the integration setup process. When setting up an integration, you can choose to exclude "Metrics" assets from being published to the Data Catalog while still ingesting the underlying data. This option helps reduce catalog clutter and makes it easier to find relevant datasets. The "Metrics" asset creation is enabled by default to maintain existing behavior.
• You can now automatically sync tolerance values from Data Quality & Observability Classic rules to Collibra Platform as threshold parameters when rules are promoted or updated. The tolerance values become visible on the rule asset in the platform. Each sync action is logged with timestamps, rule IDs, and user information for complete traceability. If syncing fails, the system logs detailed error information to help with troubleshooting.

Fixes

Platform

• Data Quality & Observability Classic now starts successfully when the SAML tenant manager is enabled. Previously, the web application failed to initialize after upgrading to version 2026.03 if SAML_TENANT_MANAGER_ENABLED was set to true.
• We added support for additional types of SAML envelope configurations.
• The Helm chart value global.web.security.jwt.token.secretkey now defaults to a sentinel value that causes a random JWT secret key to be generated at deploy time. This random key is regenerated on every application restart, which means short-term tokens issued from previous restarts will be invalidated. To maintain a consistent key across restarts, set global.web.security.jwt.token.secretkey to a custom value of at least 32 characters. Custom values shorter than 32 characters will now cause chart rendering to fail with an error.
• Users with the ROLE_ADMIN_VIEWER role can now access the Schedule Restriction page without encountering the "Failed to get schedule restrictions" error. This resolves an issue where business administrators were unable to view schedule restrictions due to insufficient permissions. The role maintains appropriate read-only access while continuing to restrict edit and delete capabilities for these users.

Jobs

• Databricks Pushdown jobs now run successfully on tables with special characters in column names.

Findings

• When exporting findings with Link IDs, the export limit now applies to each rule individually rather than to all rules collectively. Previously, if you set an export limit, the system would take the first N records from all rules combined, which could result in some rules being excluded entirely from the export if earlier rules filled the limit.

Rules

• Rule syntax validation for rules no longer fails when datasets sourced from Edge Information Core (EIC) return zero preview rows. You can now create and modify rules without encountering "No data preview available" errors. The validation process now evaluates SQL logic independently of dataset row count, ensuring consistent rule development across all data sources.
• The "Preview Breaks" dialog box now displays columns in the same order as specified in your rule query, rather than alphabetical order. This improvement applies to Databricks, Redshift, and Snowflake connections for both Pushdown and Pullup jobs, including complex queries with CTEs, window functions, and column aliases.
• The Rule Builder data preview now loads only when you select the "Data Preview" tab.
• The purpose field in data quality rules now behaves consistently across all rule types. Previously, quick rules returned an empty string ("") for the purpose field when no value was provided, while manually created rules returned null. Both rule types now handle empty purpose fields uniformly.

• New and improved
• Fixes
• Patch release

Release Information

• Release date of Data Quality & Observability Classic 2026.03: April 3, 2026
• Release notes publication date: March 9, 2026

New and improved

Platform

Important You must configure the ALLOWED_LOCAL_PATHS variable in either "owl-env.sh" or "ConfigMap" to specify all local file base paths where files, such as drivers, are stored. Ensure you set this variable for both "dq-web" and "dq-agent" configurations if the configurations are not shared.

For example: If DQ Classic is installed to /home/collibradq/owl and JDBC drivers are located at /home/collibradq/owl/drivers, then /home/dq/config/owl-env.sh should include the following:
export ALLOWED_LOCAL_PATHS=/opt/collibradq/owl

If drivers are stored in a different directory structure, such as /data/storage/owl/drivers, then you must append that to the configuration.

Important If you receive an error when loading the Explorer page for datasets, verify and update the qualified= parameter in the URL. Ensure the value is in the correct schema.table format.

• The Amazon Athena Simba JDBC driver is now updated to version 2.2.2.
• You can now pass an encrypted SAML keystore password to the SAML setup.
• The ENABLE_STRICT_TAGGING flag on the Configuration Settings > Application Config page now defaults to "false." This ensures that the behavior of metatags remains unchanged for existing customers.
• Connection URLs now include all connection parameters when rewritten with an authentication token. This ensures complete and accurate URL generation.

Jobs

• The struct column type for the SDO_GEOMETRY SQL data type is now correctly identified as "unsupported" when creating or editing datasets.

Findings

• Source export now consolidates multiple files for SOURCE_VALUE, SOURCE_COUNT, and SOURCE_SCHEMA into a single SOURCE Excel file, matching the behavior in legacy.

Rules

• The “Custom Template Rules” rule query value from Rule Builder now persists on the Findings > Rules page and the Rule Definitions page.

Dataset Manager

• You can now choose metatags from a pre-selected drop-down list when ENABLE_STRICT_TAGGING is set to "false." ENABLE_STRICT_TAGGING is set to "true," you can add your own metatags and also select from the pre-selected list. This replaces the previous t1, t2, t3, and t4 metatag fields with pre-selected and user-approved values.

APIs

• Time zone settings are now properly preserved during export and import processes when using APIs.

Collibra Platform integration

• Dimensions are now correctly assigned to layers, even if the dimension name appears multiple times in the DQ_dimension table. Duplicate dimension names are now supported, ensuring proper layer assignment when the DQ_dimension table is correctly configured.
• When you delete a rule in Data Quality & Observability Classic, it is now marked as "Deleted" in Collibra Platform instead of "Suppressed." Additionally, deleted rules are no longer included in the export object or JSON.

Fixes

Platform

• Pendo no longer causes a "pendo.clearSession()" error when logging in with a block script set to false. Additionally, Pendo does not activate upon login when it is blocked internally.

Jobs

• White spaces in dataset source queries are now handled correctly. Schema and table names now show properly in the metadata bar and the Dataset Manager page.
• You no longer receive an error message on the Explorer page when local file management configuration is disabled.

Findings

• When you re-run a job after invalidating fuzzy match duplicates, saving, and retraining on the Findings page, the job no longer contains the same invalidated fuzzy match duplicates.

Rules

• Secondary rules now support functions in the DATE_FORMAT(DATE('${rd}'), 'yyyyMMdd') query.
• Alerts are no longer blocked when an adaptive rule with an associated alert is configured to never exist. Data Quality & Observability Classic now handles the absence of adaptive rule behavior gracefully, ensuring that job re-runs do not trigger alerts or send emails. Additionally, the email processing queue isolates failures, preventing errors in one alert payload from blocking downstream alerts.

APIs

• Time zone settings are now properly preserved during export and import processes when using APIs.

Collibra Platform integration

• Dataset integration now succeeds even when metatags contain spaces. Spaces in metatag values are automatically replaced with hyphens during saving to prevent integration errors.
• The toaster message for the auto map feature now states "Tables with the provided schema <yourSchema> are not found" when no tables or views exist, instead of just stating "The schema was not found."

• New and improved
• Fixes

Release Information

• Release date of Data Quality & Observability Classic 2026.02: February 26, 2026
• Release notes publication date: January 30, 2026

New and improved

Platform

• The JobRunner version has been upgraded to 8.3.1.
• The Simba BigQuery JDBC driver is now updated to version 1.6.5.1002, and the Spark BigQuery connector is now updated to version 0.43.1.
• The Admin page for Webhook Alerts now includes new columns for "Global" and "JSON Template." These additions allow you to view the full configuration of a webhook directly in the table, eliminating the need to open each webhook for editing.
• A new security setting and user role are now available in the Findings module to provide granular control over data export capabilities. Administrators can restrict specific users from downloading or copying records to the clipboard while still allowing them to preview data in the UI.

Jobs

• You can now archive duplicate break records when using SQL Server Pushdown.
• When you rename a dataset using Dataset Manager, you now receive a notification that the process might take some time. This ensures you're informed and prevents issues caused by refreshing or navigating away during the renaming process.
• You can no longer select non-text rows when adding a "Shapes" layer during the job creation process. This ensures compatibility, as non-text rows are not supported.
• The Explorer SQL Query landing page now supports Common Table Expression (CTE) queries. CTE-based queries compile successfully and are no longer automatically escaped. Queries starting with the WITH keyword no longer require parentheses or additional whitespace around the CTE definition.
  • Known limitation: Pretty Print is not supported, and random characters entered in the SQL Query, such as "asdfasdfasf," returns an error message.
• For S3 connections using an Instance Profile, missing or expired credentials now result in an explicit error when you access the connection from the Explorer tree. This helps you quickly identify and resolve credential issues.

Findings

• You can now add or edit a rule dimension from the "Edit Rule" dialog box on the Findings page. This provides more flexibility in managing rule dimensions.
• The Source Export report now passes the label instead of the passStatus value to improve usability. This update improves usability by providing clear visual indicators for rule statuses: a green checkmark for "passing," a horizontal rule for a neutral state, and a red "X" icon for "failing."

Rules

• The preview behavior now correctly supports alias names with spaces and preserves the expected column order. Additionally, the Run Result Preview in the Rule Workbench now properly handles queries with aliases for pullup datasets.

APIs

• The /v2/putweights endpoint now accepts URL-encoded form parameters with the request type application/x-www-form-urlencoded. This enhancement ensures all current form parameters are handled correctly while maintaining the same response and behavior as the existing multipart implementation. Additionally, the server is no longer limited by maxPartCount for these requests.

Fixes

Platform

• You can now edit remote file jobs and view columns without needing ROLE_ADMIN or ROLE_CONNECTION_MANAGER privileges, as long as the environment's security settings don't explicitly require them. The URL parsing logic has been corrected to support this functionality.

Jobs

• When you delete a dataset with default dataset ownership enabled, other datasets that include the original dataset name are no longer removed from default owner access. This ensures that datasets remain accessible to their owners.
• For complex queries, the correct schema and table name are now pulled from the query and placed in the metabar accurately.
• You can now validate source mapping on columns that have spaces or special characters in their names.
• The SCHEDULE_ENABLED flag now properly disables the job scheduler. When the flag is set to FALSE, the scheduled jobs no longer run.

Findings

• You no longer encounter ORA-01830 syntax errors in Oracle datasets when using time-based outlier bins. Date strings with time components are now handled properly, ensuring accurate date formatting.

Alerts

• The Rule Details table in email alerts now correctly shows all rows for conditional alerts with multiple conditions connected by and or or. For example, multi-alert conditions such as score > 75 AND find_valid_rules > 20 are now fully supported.