September 2026
The 2026.5.0 release adds support for AWS-hosted Databricks environments, Databricks data transfer, and KVM deployment for the Oracle connector (Early Access).
On this page:
New features
-
AWS support for the Databricks connector
The Databricks connector now supports AWS-hosted Databricks environments with managed tables backed by Amazon S3. This extends the existing support for Azure-hosted Databricks environments with ADLS Gen2-backed managed tables.Catalog authentication continues to use OAuth M2M. AWS storage authentication supports IAM instance roles through
AWS_ROLEand access keys throughAWS_SECRET. For configuration details, see Databricks connector overview, Databricks supported features, Permissions and access requirements, and API reference and examples. -
Databricks data transfer
The Databricks connector now supportsDATA_TRANSFERjobs, which copy selected Delta data to a target environment without masking it. You can use the same filtering options available for masking jobs, including partition and time-based filters, to move or refresh a subset of tables between environments. For more information, see Databricks supported features. -
KVM deployment for the Oracle connector (Early Access)
The Oracle connector now supports deployment on any KVM-based hypervisor whose vendor supports Ubuntu 24.04 as a guest operating system. This is available as an Early Access (EA) feature. For more information, see Supported platforms (virtual appliance), Installation (virtual appliance), and Technical requirements (virtual appliance).
Fixed issues
| Issue number | Summary |
|---|---|
| HM-6295 | Resolved an issue with column mapping validation and improved support for masking tables that use primary keys in the Snowflake connector. |
| HM-7224 | When you configure the Snowflake connector on a closed-appliance deployment, private keys, passphrases, and personal access tokens (PATs) are now encoded automatically. You no longer need to encode these values manually. |
| HM-7244 | Fixed an issue where a Databricks masking job in the CANCEL_INITIATED state could leave a subsequent job stuck in progress because masking never started. |
| HM-11283 | Resolved an issue that prevented Snowflake connector properties from being updated through the Connector Properties API on closed-appliance deployments. The unload and load service configurations are now separate. |
| HM-11852 | Resolved an intermittent issue in the masking service that could prevent the masking workload from being assigned to masking engines during an execution. |
| HM-12014 | Resolved an issue that rejected Instant Client zip files uploaded from Windows browsers because they used the application/x-zip-compressed file type. |
| HM-12232 | Fixed an issue with cross-process locking for a split file masking job in the File connector load service. |
Known issues
| Issue number | Summary | Workaround |
|---|---|---|
| HM-5101 | Dataset creation does not currently support payloads or file uploads containing more than 10,000 items. Any attempt to upload files exceeding this limit will fail. | None |
| HM-3636 | MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response. | None |
| HM-1397 | Oracle Load fails for table having triggers only with SQL*Loader-937 error. | None |
EOL (end-of-life) notice
File Connector Profiler service
The File Connector Profiler service reached end of life (EOL) in the 2026.5 release.
Docker Compose - November 2026
Docker Compose deployments for Hyperscale Compliance reach End of Life (EOL) in November 2026. For more information, see Deprecated and EOL notices.