17.1.0 Patch Releases
Improvements and fixes released for Ataccama ONE 17.1.0 since the initial release in June 2026.
For new features and enhancements, see 17.1.0 Release Notes.
September 2026
Patch 11
ONE
Metadata Management Module
-
Exporting profiling and DQ insights to a Microsoft Excel file no longer fails when a catalog item has attributes whose names differ only in letter case.
-
You can now use Amazon Bedrock to connect to the DQ&C MCP server.
ONE Runtime Server
-
Logging in to ONE Runtime Server no longer fails intermittently with a
Remote host terminated the handshakeerror that previously required a restart to clear. -
Reconnection attempts in the Notification handler now back off after repeated failures. Previously, a dropped connection could cause endless retries every few seconds, flooding logs with
ApolloNetworkException: Network errormessages and, in some cases, exhausting ONE Runtime Server memory until it was restarted.
Patch 10
ONE
ONE Web Application, Metadata Management Module, Data Processing Module, Data Processing Engine, Audit Module
-
Reading tables through SAP RFC connections no longer fails when a
DATE,TIME, orUTCLONGfield contains a value that cannot be parsed, or when a field value is truncated by SAP. Such values are returned asnullwith a warning, and a truncated value in one column no longer discards the valid values in the other columns of the same row. -
Failed profiling jobs in Processing Center show the error from the Data Processing Engine (DPE) instead of only
Job '<item>' failed. Failed jobs of any type no longer show an empty ornullreason for failure, and jobs that fail no longer remain in the Running state. -
Scheduled runs no longer fail with
Unexpected error occurred, job failed in the transaction roll-backwhen the user who created the schedule has lost edit access to it. -
Metadata import completes faster when the source has no catalog item relationships or the import returns no items. Previously, such an import refreshed the database statistics for every table in the metadata database, which could take several minutes in large environments.
-
The Ataccama ONE version under My Account > Version Information shows the exact patch version (for example,
17.1.0-patch10instead of17.1.0). -
Upgraded third-party dependencies in the ONE Web Application, Audit Module, Data Processing Module (DPM), Data Processing Engine (DPE), and DPE JDBC drivers for enhanced security and stability.
August 2026
Patch 9
ONE
ONE Web Application, Metadata Management Module, Data Processing Engine, Data Quality Firewall, ONE Data, Comments
-
Changes to entity screen layouts can be saved and published again if you’re using JSON5 syntax. Previously in 17.1.0, saving failed with a JSON parsing error on screens whose layout configuration uses this syntax.
-
Exporting invalid records from pushdown DQ evaluation now works for aggregation rules grouped by two or more attributes. Previously, the export target table was left empty even though DQ evaluation reported success.
-
Faster publishing of assets that have a data steward assigned: access permissions are no longer recomputed for the whole asset subtree when the steward is unchanged.
-
In Ataccama Cloud environments, database connection pools now recover after an Amazon Aurora topology change instead of requiring a service restart.
Patch 8
ONE
Metadata Management Module, Data Processing Engine, Audit Module, Lineage Scanning Service
- Data quality evaluation
-
-
DQ evaluation in pushdown processing no longer fails when many catalog items share a connection and the connection pool is temporarily exhausted. DQ evaluation now waits for a free connection and retries with backoff, matching pushdown profiling.
-
Monitoring projects that combine a Spark Writer post-processing plan with another transformation plan no longer fail with
Step cannot run locally [Spark Writer]. Previously, the job was incorrectly run locally instead of on Spark. -
DQ evaluation on a source processed on Spark no longer incorrectly runs on zero records while reporting success. Previously, such jobs could finish successfully with all DQ results empty (N/A) and write an empty target table.
-
- Ataccama Cloud
-
-
Hybrid Data Processing Engine (DPE) now connects with encryption enabled in Ataccama Cloud environments. Previously, required encryption properties were missing from its configuration, so the connection failed.
-
In Ataccama Cloud environments on AWS, connections to Amazon Aurora from the Metadata Management Module and Audit Module no longer fail permanently after an Aurora topology change, such as a failover.
-
Ataccama Cloud environments on Azure now support Azure Private Link ingress for the Metadata Management Module.
-
- Security
-
-
Upgraded third-party dependencies in the Data Processing Engine for improved security and stability.
-
- Other fixes
-
-
Publishing a large change set, such as a bulk delete that cascades to hundreds of thousands of records, no longer runs for many hours or blocks scheduled jobs while it completes.
-
Importing metadata that contains ambiguously matched nodes (for example, a monitoring project export) no longer fails with a database error and no validation report. The ambiguous matches are now recorded in the validation report and the import completes in error-tolerant mode.
-
Lineage scan runs no longer get stuck in
CREATEDand fail to start when a scan plan references two or more credentials. Previously, the affected scan plan became permanently unusable on its edge and had to be recreated.
-
Patch 7
ONE
Metadata Management Module, Data Processing Engine, Data Processing Module, ONE Data
-
You can now preview tables and columns using interactive credentials while browsing a database, without requiring default credentials.
-
Users now keep their access to data remediation output tables in ONE Data between data remediation runs. Previously, repeated data remediation runs could remove the shared access.
-
Upgraded third-party dependencies in the Data Processing Engine (DPE), Data Processing Module (DPM), and ONE Runtime Server for enhanced security and stability.
MDM
-
MDM now supports connecting to Google BigQuery data sources through an additional driver. See Loading Additional Drivers.
July 2026
Patch 6
ONE
ONE Web Application, Metadata Management Module, Data Processing Engine, Audit Module, Metadata Extraction Service, MDE Database Migration
- Catalog & data processing
-
-
The credentials Overview tab now shows the credential type so you can easily tell which type of credentials a specific connection uses.
-
Tableau catalog items hosted on the default site (with an empty site content URL) now correctly show report preview instead of failing to load.
-
Users with View metadata access level on a catalog item can no longer edit the catalog SQL query. Previously, the query appeared editable even though changes could not be saved.
-
You can now create a single review request task covering multiple unpublished catalog items at once from the Catalog Items > Unpublished tab, instead of submitting each item for review individually. This was already possible for terms, monitoring projects, and rules.
-
- Search & display
-
-
Full-text search now returns correct results when searching for assets whose names contain underscores (
_). -
Searching the group hierarchy on the User Management > Groups screen no longer fails with a
Cannot read properties of null (reading 'childGroupCount')layout render error when the group is nested more than two levels deep in the organization. -
The Terms screen now loads when its search configuration indexes a computed content property as a child node. Previously, publishing this configuration could prevent the screen from loading and showed a
Renderer for column "name" not founderror instead.
-
- Upgradability and performance
-
-
In self-managed deployments, upgrading from 17.0.0 to 17.1.0 no longer fails during Metadata Extraction Service database migration when the database connection URL includes query parameters alongside
currentSchema. Previously the migration failed withtype "operation_step_type" does not exist. -
In Ataccama Cloud environments using AWS PrivateLink, writing a catalog item to ONE Data no longer fails after upgrading to 17.1.0.
-
Optimized resource usage for sleeping environments in Ataccama Cloud.
-
- Authentication & security
-
-
Upgraded third-party dependencies in ONE Web Application and Audit Module for enhanced security.
-
Patch 5
ONE
ONE Web Application, Metadata Management Module, Metadata Extraction Service, MDE Database Migration
-
After upgrading to 17.1.0, monitoring projects whose post-processing plan includes a Database Output step no longer fail validation with
There is no attribute named 'not_applicable_rules' in the catalog item. The not-applicable result columns are now added only when the project has a rule that can produce a not-applicable result, so existing plans validate and run without changes. -
Fixed an issue where exporting a large lineage dataset to CSV could run out of memory and leave a database connection open, which could block other database operations (such as backing up the database in the web application).
-
Replying to a comment no longer breaks the layout and hides the comments panel.
Patch 1
ONE
ONE Web Application, Metadata Management Module, Workflow Service, AI Evolution
-
Group stewardship assignments on rules, monitoring projects, and terms are now included when exporting and importing metadata. On import, groups are matched to existing groups rather than created, and the import fails if a referenced group is missing. Single-user stewardship is not exported.
-
Fixed an issue where a review request task could become stuck, showing the View Review Request window with no way to approve or reject the changes.
-
Faster metadata imports of large content packs, such as the demo data pack, which previously could take up to 20–25 minutes.
-
Chat with documentation now returns answers and links based on the current 17.1 documentation.
-
Fixed an issue where opening a nested login callback URL could send the browser into an infinite refresh loop instead of loading the application.
-
Security fix for MinIO.
Was this page useful?