2026.2 release notes

March 2026

This 2026.2 release adds Virtual Appliance support for MongoDB connector, introduces Snowflake support for importing masking profiles from the Continuous Compliance Engine, and adds role based authentication to the S3 compatible file connector.

On this page:

New features
Fixed issues
Known issues
EOL (end-of-life) notice

New features

New VM Appliance deployment method (MongoDB)
Hyperscale now supports a VM-based appliance deployment option in addition to the existing Kubernetes model for new deployments of Hyperscale Compliance.
The VM appliance model follows the structure of the traditional engine based hosting model and provides a more straightforward management experience for administrative teams.

Administrators can perform core system management tasks through the appliance interface, including:
- Storage management
- Network management
- Network security (KeyStore and TrustStore management)
- Support bundle generation
VM-based deployment is available to Oracle, MSSQL, and MongoDB connectors.

Hyperscale profile job sync feature for Snowflake
This release adds Snowflake support for importing masking profiles from the Continuous Compliance Engine. To use this feature, you must configure a third-party Snowflake JDBC driver with the Compliance Engine as an extended connector. Refer to How to sync a Hyperscale job for additional information.

File connector enhancements
The S3‑compatible connector now supports STS, IRSA and INSTANCE based authentication. For more information, refer to S3-compatible connector and user permissions.

Fixed issues

Issue number	Summary
DLPXECO-13141	Fixed an issue where the file connector previously failed or behaved unpredictably when ingesting Parquet files that contained the logical types INT64 (TIME(MICROS,false)) or INT64 (TIMESTAMP(NANOS,false)). Hyperscale now supports all Parquet field types that are currently supported by the Continuous Compliance Engine including INT64 timestamp with nanoseconds.
DLPXECO-13521	Fixed an issue that caused jobs with split count = 1 to fail when the source and the S3 staging area were hosted in AWS. For S3 staging with split count = 1, the unload process now uses the driver instead of a manual copy.

Issue number

Summary

DLPXECO-13141

Fixed an issue where the file connector previously failed or behaved unpredictably when ingesting Parquet files that contained the logical types INT64 (TIME(MICROS,false)) or INT64 (TIMESTAMP(NANOS,false)).

Hyperscale now supports all Parquet field types that are currently supported by the Continuous Compliance Engine including INT64 timestamp with nanoseconds.

DLPXECO-13521

Fixed an issue that caused jobs with split count = 1 to fail when the source and the S3 staging area were hosted in AWS. For S3 staging with split count = 1, the unload process now uses the driver instead of a manual copy.

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

Docker Compose - May 2026

Docker Compose deployments for Hyperscale Compliance will reach End of Life (EOL) in May 2026. For more information, refer to Deprecated and EOL notices.