Ataccama 17.0.0 Release Notes

Re-importing a monitoring project configuration with SQL catalog items after editing the project configuration no longer fails due to duplicate catalog item entries in the export file.

Overall data quality results for sections in the monitoring project Report tab now correctly exclude dimensions that do not contribute to overall data quality.

When creating a DQ firewall from a catalog item, attributes with unsupported data types are now skipped instead of blocking firewall creation entirely. A warning lists any skipped attributes.

Fixed intermittent ConcurrentModificationException failures in JDBC Reader and SQL Execute steps, sometimes surfacing as "Cannot connect to the database" errors despite the database being healthy. The issue was caused by a race condition when multiple jobs ran concurrently.

When editing rule configuration, conditions with functions or expressions not supported by Snowflake pushdown are now correctly marked. Rules with such conditions are excluded from evaluation in Snowflake pushdown.

IOMETE pushdown processing now uses the ArrowFlight JDBC driver instead of the deprecated Hive JDBC driver.

IOMETE pushdown processing can be selected as an experimental feature for version 17.0.0 in Ataccama Cloud environments.

Chat with documentation now links to the correct documentation version.

Increased internal token limits for AI-assisted generation of SQL queries and rule logic, reducing the likelihood of failures when generating longer outputs.

Faster loading on multiple screens:

Improved DPM database query performance, reducing unnecessary load on the DPM database.

Improved audit module write performance by switching to time-ordered identifiers for audit records.

Fixed an issue where DPE slots were incorrectly reported as fully utilized, causing queued jobs to stall indefinitely.

Thread dumps now include additional per-thread diagnostics, such as memory allocation and class loading statistics, for improved troubleshooting.

In Ataccama Cloud environments, the PostgreSQL monitoring exporter now correctly loads custom metric queries from the configuration, ensuring all configured database metrics are collected as expected.

Security fixes for ONE Web Application.

Anomaly detection on the Profile & Insights tab displays the expected values correctly.

Anomaly detection pop-up notifications now display correctly.

Profile inspector no longer shows mixed results when monitoring projects target the same catalog item with and without data slices. Results now correctly reflect whether the project uses the full dataset or a specific data slice.

Monitoring projects with post-processing plans deactivated no longer remain in the post-processing status indefinitely due to duplicate filters. A validation error now prevents publishing duplicate filters on the same attribute.

Manual runs of monitoring projects no longer fail after rule modifications.

Monitoring projects no longer fail after DQ dimension rename.

When importing monitoring project configuration containing filters, filter references to catalog items and attributes are correctly updated after remapping. Previously, filters would appear invisible after remapping but were still submitted to DQ evaluation as duplicates, causing exponential growth in filter combinations and processing failures.

When reimporting the same monitoring project configuration but with a post-processing plan attached, related catalog items are no longer duplicated and the project runs as expected.

Long path names on the monitoring project Notifications tab do not overflow.

DQ filters in monitoring projects now work correctly with pushdown enabled.

Long rule explanations on the monitoring project Report tab do not overflow.

Monitoring project results in email notifications are now rounded to two decimal places.

Updating individual data quality checks using the Update rule option in the DQ check modal works as expected. Previously, the update would fail to be propagated.

Scheduled monitoring projects do not fail even if the Data Processing Engine (DPE) is temporarily disconnected when the run starts.

When using transformation plans to export monitoring project results to a database or a CSV file, invalid and valid columns are correctly populated for failing rules instead of containing only null values.

Rule suggestions now correctly respect your access permissions when using the Check for rule suggestions option. You’ll see suggestions for catalog items you have access to (even without term access), while rules requiring higher permissions are excluded.

Rule suggestions load correctly in monitoring projects for catalog items with assigned rules or terms you don’t have access to.

Removed the non-functional Apply the following rules automatically on all attributes with this term option from the term Settings tab. Rules are always applied when a term is assigned to an attribute.

A rule detail page loads correctly when opened from the Rule suggestions screen.

Rule suggestions on the attribute Profile & DQ insights tab do not overflow.

Data quality rules containing regular expressions now produce consistent results between rule debugging and DQ evaluation.

Context help consistently shows for functions in the Rule Builder.

Pushdown profiling now shows which rule and lookup caused the failure when a referenced lookup hasn’t been built.

Transformation plan previews are generated for all plans with at least one valid step, even if they contain invalid steps.

In transformation plans, Stewardship can now be edited for governance roles with the Full access level.

Data slices in monitoring projects now include null values.

Data slices are supported for Databricks catalog items.

The Create data slice option is correctly hidden for users with view-only access to the catalog item.

Power BI report previews load reliably without intermittent errors.

Setting a custom preview for a Power BI report no longer deactivates the Open in reporting tool option.

The Schemas screen reflects term updates more quickly after modifications.

Attribute IDs on SQL catalog items imported from content packs are now preserved when editing the query.

A warning is displayed when attempting to delete a catalog item that is referenced by a monitoring project.

Fixed an issue where DQ evaluation failed with DataSourceClientConfig not found error even after profiling completed successfully.

DPM no longer crashes when post-processing very large profiling results, such as tables containing huge JSON values.

After upgrading, Sweep documentation flow now appears in the documentation flow menu.

When a documentation flow is discarded, the corresponding jobs are now canceled.

The Delete all option in the Sweep documentation flow deletes all obsolete catalog items, not just those on the current page.

Users with full access level to a source can run the Sweep documentation flow.

Long term names do not overflow the Relationships widget.

The term Occurrence tab displays correctly regardless of metadata model property configurations.

Term Suggestions services no longer overload application logs with zero-confidence term suggestions.

Term Suggestions metrics are no longer collected when the services are not configured.

Fixed an issue where an error was shown instead of creating a Review task when non-admin users requested reviewing and publishing of changes.

Loading to ONE Data works correctly for data with null or empty values of DateTime data type.

Deleting interactive credentials from a source connection no longer prevents the connection from publishing.

File import settings no longer appear on database connections.

Snowflake JDBC connections now time out properly when the target host is unreachable, instead of leaving DPE threads stuck indefinitely.

When using Snowflake OAuth credentials, the token validity is derived from the OAuth response.

Databricks JDBC connections using integrated credentials work correctly after upgrading.

Databricks pushdown processing works as expected when operational credentials are used.

Databricks jobs execute successfully when the ADLS path contains spaces in folder names.

Fixed an issue where profiling failed on Databricks JDBC connections after upgrading to 16.3.0-patch3, caused by internal properties being incorrectly passed to the Databricks driver.

Workflows no longer fail when runtime configuration contains empty passwords or other secrets.

Fixed an issue where importing folders from ADLS failed to browse nested path levels correctly and created catalog items at the folder level instead of for individual files.

BigQuery pushdown processing now displays the correct source name in error messages.

Canceling pushdown data quality jobs now immediately stops running database queries.

Azure Key Vault authentication settings are no longer lost when upgrading from 15.4.1, which previously caused connections using secret management to fail.

Export to database no longer fails after upgrading to v17.

Keycloak now starts successfully when using a custom monitoring port.

Set the default logging level for hybrid DPEs to DEBUG.

Improved hybrid DPE stability during high memory usage.

Fixed 'user is null' messages flooding logs on some environments.

Self-managed deployments now support IAM authentication for the ONE database connection, with automatic token refresh.