> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/release-notes/data-quality-observability-self-hosted-release-archive/release-2025-07.md). # Release 2025.07 * [Announcement](#announcement) * [New and improved](#new-and-improved) * [Fixes](#fixes) * [Patch release](#patch-release) ## Release information * Release date of Data Quality & Observability (self-hosted) 2025.07: August 4, 2025 * Release notes publication date: July 8, 2025 ## Announcement {% hint style="warning" %} As a security measure, we are announcing the end of life of the Java 8 and 11 versions of Data Quality & Observability (self-hosted), effective in the August 2025 (2025.08) release.**In this release (2025.07)**, Data Quality & Observability (self-hosted) is only available on Java 17 and Spark 3.5.3. Depending on your installation of Data Quality & Observability (self-hosted), you can expect the following in this release: * **Kubernetes installations** * Kubernetes containers automatically contain Java 17 and Spark 3.5.3. * If you use custom drivers, ensure they are compatible with Java 17 and Spark 3.5.3. * If you use file-based SAML authentication with the `SAML_METADATA_USE_URL` variable set to `false` in the owl-web ConfigMap, update the Meta-Data URL option on the SAML Security Settings page with your metadata file. Use the **file:/opt/owl/config/idp-metadata.xml** format, ensuring the file name begins with the prefix **file:**. For steps on how to configure this, go to the "Enable the SAML SSO sign in option" section in [Configuring SAML authentication](/data-quality-self-hosted/security-configuration/saml-authentication/configuring-saml-authentication.md). * **Standalone installations** * To install Data Quality & Observability (self-hosted) 2025.07, you must [upgrade to Java 17](https://support.collibra.com/hc/en-us/articles/29404286691991-Upgrading-Java-on-CentOS-RHEL-7-8-or-9) and [Spark 3.5.3](/data-quality-self-hosted/installation/agent/upgrade-spark.md). * If you use custom drivers, ensure they are compatible with Java 17 and Spark 3.5.3. * Follow the latest [steps to upgrade](/data-quality-self-hosted/installation/upgrade-data-quality-observability-self-hosted/upgrade-collibra-data-quality-observability.md) to Data Quality & Observability (self-hosted) 2025.07 with Java 17. * If you use file-based SAML authentication with the `SAML_METADATA_USE_URL` variable set to `false` in the owl-env.sh script, update the Meta-Data URL option on the SAML Security Settings page with your metadata file. Use the **file:/opt/owl/config/idp-metadata.xml** format, ensuring the file name begins with the prefix **file:**. For steps on how to configure this, go to the "Enable the SAML SSO sign in option" section in [Configuring SAML authentication](/data-quality-self-hosted/security-configuration/saml-authentication/configuring-saml-authentication.md). * We encourage you to migrate to a Kubernetes installation to improve the scalability and ease of future maintenance. In this release, only critical and high-priority bug fixes will be made for Java 8 and 11 versions of Data Quality & Observability (self-hosted). For a breakdown of Java and Spark availability in current and upcoming releases, click "See what is changing" below.

See what is changing

| Data Quality & Observability (self-hosted) version | Java 11 | Java 17 | Java 21 | Spark versions | Additional notes | | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ----------------------------------------------------------------------------------------------------- | | 2025.08 |

No |

Yes |

No |

Yes |

No |

Yes |

No |

Yes | 4.1.0 only | |

For more information, go to the [Data Quality & Observability (self-hosted) Java Upgrade FAQ](https://support.collibra.com/hc/en-us/articles/27421373124503-Collibra-Data-Quality-Observability-Java-upgrade-FAQ). {% endhint %} ## New and improved ### Platform {% hint style="info" %} We updated Tomcat to address several security vulnerabilities (CVEs). The maximum part size for multipart requests is now set to 80 by default. This default limit might affect APIs that process datasets with an large number of columns. If necessary, you can change this limit using the property "DQ\_SERVLET\_MULTIPART\_MAXPARTCOUNT" in the owl-env.sh file for Spark Standalone installations or the owl-web-configmap for Kubernetes environments. {% endhint %} * You can now use the [dataset security setting](/data-quality-self-hosted/admin-configuration/admin-console/security-settings.md) "Require TEMPLATE\_RULES role to add, edit, or delete a rule template" and assign users the ["ROLE\_TEMPLATE\_RULES" role](/data-quality-self-hosted/admin-configuration/admin-console/role-management/role-management.md) to restrict updates to template rules. (idea #CDQ-I-169) * When "Require TEMPLATE\_RULES role to add, edit, or delete a rule template" is enabled, users without the "ROLE\_ADMIN" or "ROLE\_TEMPLATE\_RULES" roles can view the list of template rules but cannot add, edit, or delete them. * If "Require TEMPLATE\_RULES role to add, edit, or delete a rule template" is disabled, or if it is enabled and the user has "ROLE\_ADMIN" or "ROLE\_TEMPLATE\_RULES," they can view, add, edit, and delete rule templates. * When creating a job, the “Visualize” function in Explorer is now inaccessible if the [dataset security setting](/data-quality-self-hosted/admin-configuration/admin-console/security-settings.md) "Require DATA\_PREVIEW role to see source data" is enabled and the user doesn't have the "ROLE\_DATA\_PREVIEW" role. * You can now use SAML SSO to sign in from the Tenant Manager page. Additionally, the AD Security Settings page from the Admin Console is now available in the Tenant Manager, allowing you to map user roles to external groups. * The application now has improved security when parsing SQL queries in the Dataset Overview and the "SQL View" step in Explorer. As a result, new or edited datasets with complex queries may not pass validation during parsing if they include nested subqueries, non-standard syntax, or ambiguous joins that are not supported by the parser's grammar. ### Jobs * You can now scan for duplicate records in [Oracle Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) jobs. * When you [transform](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job/transform.md) a column from Explorer, it is now available in the “Target” drop-down list during the [Mapping](/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job/mapping.md) step. * When a job fails, the metadata bar remains visible on the Findings page. ### Rules * The “[Edit Rule](/data-quality-self-hosted/core-concepts/dq-rules/rule-builder/working-with-the-rule-workbench/create-a-data-quality-rule.md)” dialog box now includes Description and Purpose fields. These fields allow you to add details about Collibra Platform assets associated with your rule and identify which assets should relate to your Data Quality Rule asset upon integration. (idea #CDQ-I-219) * The Rule Workbench now supports the substitution of both string and numeric data types for $min, $average, and $max stat rule values. * The Results Preview on the Rule Workbench now shows columns in the same order as they are listed in the rule query. For example, the query `select SYMBOL, VOLUME, LOW, HIGH, CLOSE, OPEN from PUBLIC.NYSE where SYMBOL IS NOT NULL LIMIT 3` displays the columns in the following order in the Results Preview: * SYMBOL * VOLUME * LOW * HIGH * CLOSE * OPEN ### Alerts * You can now [create alerts for adaptive rules](/data-quality-self-hosted/core-concepts/alerts/managing-alerts-from-the-alert-builder.md) from Pullup jobs in the “Breaking” state. This eliminates the need to manually search for breaking records in adaptive rules, reducing the risk of missing them. (idea #DCC-I-609, DCC-I-2713, CDQ-I-199, CDQ-I-105) * [Condition alerts](/data-quality-self-hosted/core-concepts/alerts/working-with-the-alert-builder/adding-dataset-alerts.md) now include a "Condition Value" field to provide more context about the reason for the alert. For example, the Condition Value for a row count check might be rc = 0, while for an outlier score, it could be outlierscore > 25. (idea #CDQ-I-317) * When you create a new alert with a name already in use by another alert on the same dataset, the existing alert is no longer automatically replaced. Instead, a confirmation dialog box now appears, allowing you to choose whether to overwrite the existing alert. ### Profile * The correlation heatmap in the Correlation tab of the [Profile page](/data-quality-self-hosted/core-concepts/profile.md) now shows a maximum of 10 columns, regardless of the number of columns returned in the API response. * The “Quality” column on the [Profile tab](/data-quality-self-hosted/core-concepts/profile.md) is now renamed to “Completeness/Consistency.” ### Collibra Platform Integration * When you rename a job from Data Quality & Observability (self-hosted) that is integrated with Collibra Platform, the corresponding domains in Collibra Platform are now renamed to match the new job name. * When you add, update, or remove meta tags from a job in Data Quality & Observability Classic with an active integration to Collibra Platform, the import JSON and the corresponding Data Quality Job in Collibra Platform are now updated. The updated JSON can include up to 4 meta tags. ### APIs * The GET /v3/datasetDefs API call now returns meta tags in the array response in the same order they are set in the Dataset Manager. For example, if the first meta tag input field in the Dataset Manager contains "DATA," the second and third fields are empty, and the fourth contains "QUALITY," the array response will return: ``` “metaTags”: [ “DATA”, null, null, “QUALITY”, ], ``` ### Admin Console * You can now control the maximum allowed temporary file size using the new "maxfileuploadsize" [admin limit](/data-quality-self-hosted/admin-configuration/admin-console/configuration-settings/admin-limits.md). The default value is 15 MB. * When you enable the "RULE\_FILTER" setting in the [Application Configuration Settings](/data-quality-self-hosted/admin-configuration/admin-console/configuration-settings/application-configuration-settings.md) page, create a rule with a filter, and then disable the "RULE\_FILTER" setting before rerunning the job, the results on the Findings page still reflect the rule using the filter. * When you delete a role, any datasets mapped to it are now removed. Previously, the relations between the role, datasets, and users were still shown in the UI after deleting the role. * Orphaned dataset-run\_id pairs are now removed from the “dataset\_scan” table when you use a [time-based data retention](/data-quality-self-hosted/admin-configuration/admin-console/data-retention-policy.md) purge. ## Fixes ### Platform * You no longer encounter unexpected errors with SAML/SSO, rules, and Pushdown after upgrading to some Spark standalone self-hosted instances of Data Quality & Observability (self-hosted). * Group-based role assignments for Azure SSO now work correctly after upgrading Data Quality & Observability (self-hosted). Users no longer receive only the default "ROLE\_PUBLIC," ensuring proper access permissions. * Users with the "ROLE\_PUBLIC" and "ROLE\_DATA\_PREVIEW" roles can no longer create and save rules, ensuring role restrictions are enforced as intended. ### Connections * You can now run jobs on Teradata connections without requiring the DBC.RoleMembrs.RoleName permission. ### Jobs * Alias names now appear for date fields during row selection for a new job. * You no longer see the "Pushdown Count" option on the Mapping Configuration page. This was removed for BigQuery because it is not supported by Google. * Datasets with missing run IDs now appear in the global search. ### Rules * Rule findings using a rule filter for Pushdown jobs now show the correct subset of rows applied for the rule, instead of the total rows at the dataset level. ### Findings * Boolean attributes now show their values correctly in the Result Preview on the Rule Workbench screen. * The handling of “shape/enabled” and “deprecated profile/shape” JSON flags in dataset definitions and job runs is now consistent. * When a column contains multiple shape findings, the data preview is now shown as expected when you expand a shape finding. ### Profile * Profiling activities now correctly support profile pushdown on BigQuery, ensuring accurate and efficient data profiling. ### Reports * Encrypted columns now appear correctly on the Dataset Findings report. ### APIs * The /v3/rules/{dataset}/{ruleName}/{runId}/breaks API now returns a “204 No Content” HTTP status code during pullup jobs when a rule has no break records linked to a specific LinkID. ## Patch release ### 2025.07.1 * You can now control the strictness of SQL query validation in the Dataset Overview and in the SQL View step in Explorer. [Add](/data-quality-self-hosted/admin-configuration/admin-console/configuration-settings/application-configuration-settings/adding-custom-application-settings.md) the "VALIDATE\_QUERIES" and "STRICT\_SQL\_QUERY\_PARSING" settings in the Application Configuration Settings page of the Admin Console to configure this behavior. When "VALIDATE\_QUERIES" is enabled, you can choose between simple or strict validation via the "STRICT\_SQL\_QUERY\_PARSING" setting. Simple validation checks if the query contains any keywords other than `SELECT`, while strict performs a full syntax check to ensure the query is a valid `SELECT` statement with no non-`SELECT` keywords. If both settings are disabled, SQL query validation is turned off. For more information about how this works, go to [Application Configuration Settings](/data-quality-self-hosted/admin-configuration/admin-console/configuration-settings/application-configuration-settings.md).