6.0.0.0 release
This release supports the following feature/features:
-
New file based endpoints
-
file-download: This release introduces a new API endpoint to download the execution and dataset responses. For more information, refer to the Hyperscale Compliance API documentation.
-
file-upload: This release introduces a new API endpoint to upload a file that currently can be used to create or update the dataset using POST /data-sets/file-upload and PUT /data-sets/file-upload/{dataSetId} endpoints. For more information, refer to the Hyperscale Compliance API documentation.
-
-
MSSQL database scalability improvements
This release improves the overall job performance by adding the handling of primary key constraints.
5.0.0.1 releases
5.0.0.1 is a patch release specifically aimed at addressing a critical bug. For more information, see Fixed issues .
5.0.0.0 release
This release supports the following feature/features:
-
MS SQL connector
This release adds the MS SQL connector implemented as separate services that include unload and load services. These connector services enable Hyperscale Compliance for MS SQL databases. -
New execution endpoints
This release adds a new API GET endpoint (/executions/{id}/summary) to the existing JobExecution API to get the overview of the progress of a Job Execution. In addition to this, the existingGET /executions/{id}endpoint has been extended to have additional filters based on the task name and the task's metadata object's status. For more information, refer to the Execution API in the Hyperscale Compliance API section. -
Multi-column algorithm support
With this release, Multi-Column Algorithms can also be provided in the/data-setsendpoint. For more information, refer to the Dataset API in the Hyperscale Compliance API section. Additionally, existing Continuous Compliance jobs containing multi-column algorithm-related fields can now be importedvia/importendpoint.
4.1.0 release
This release supports the following feature/features:
-
Capability to limit the number of connections
This release adds the capability to limit the number of connections to the source and target databases using the new API parameters as Max_concurrent_source_connection and Max_concurrent_target_connection under new source_configs and target_configs respectively. Using this property, you can fine-tune the number of connections as per source target infra to get better performance. For more information, refer to the Hyperscale Compliance API documentation. -
Increased API object limit
This release increases the API object limit from 1000 to 10000.
4.0.0 release
This release supports the following feature/features:
-
Hyperscale job sync
This release adds the ability to:-
Import masking jobs inventory from Continuous Compliance engines into connector and dataset info of Hyperscale Compliance Engine with the sync Accessing the Hyperscale Compliance API endpoint.
-
Import global settings that include Algorithms/Domains from Continuous Compliance Engines to Hyperscale Clustered Continuous Compliance Engines using the sync Accessing the Hyperscale Compliance API endpoint.
For more information, refer to the How to sync a Hyperscale job section.
-
-
Add configuration properties through .env file
This release adds an additional capability to override commonly used configuration properties through the .env file. You can now update application properties in this file before starting the application. For more information, refer to the Configuration settings section.
3.0.0.1 release
3.0.0.1 is a patch release specifically aimed at addressing critical bugs. For more information, see Fixed issues .
3.0.0.0 release
This release supports the following feature/features:
-
Oracle connector
This release includes the Oracle connector implemented as separate services, including unload and load services. These connector services enable Hyperscale Compliance for Oracle databases. -
Parallel processing of tables
This release processes all tables provided through the data-set API in parallel through the four operational stages - unload, masking, upload, and post-load to minimize the total time it takes to mask the complete data set. -
Monitoring
This release provides monitoring APIs so that you can track the progress of tables in your data set through the unload, masking, upload, and post-load phases. This API also provides a count of rows being processed through different stages. -
Restartability
This release includes the ability to restart a failed process. -
Clean up
This release supports cleaning data from previous job execution.
2.0.0.1 release
2.0.0.1 is a patch release specifically aimed at addressing critical bugs and has the following updates:
-
Upgraded spring boot version to 2.5.12.
-
Minor view-only changes in swagger-based API client.
2.0.0 release
2.0.0 is the initial release of Hyperscale Compliance. Hyperscale Compliance is an API-based interface that is designed to enhance the performance of masking large datasets. It allows you to achieve faster masking results using the existing Delphix Continuous Compliance offering without adding the complexity of configuring multiple jobs.