This task triggers a Compliance job to run using the Hyperscale execution path, distributing the workload across multiple Compliance Engines.
When to use this task
Use this task to start a Compliance job as a Hyperscale execution. When Hyperscale execution is specified, the job follows the Hyperscale masking pipeline instead of the standard single-engine path. If no execution type is specified, the job runs as a standard execution by default.
Before you begin
Verify the following conditions:
-
The Compliance job has Hyperscale processing enabled and a valid Hyperscale orchestrator configured.
-
At least one Compliance Engine is assigned to the Hyperscale instance.
Steps
-
Confirm all prerequisites listed above are met.
-
Submit the execution request for the Compliance job, specifying Hyperscale as the execution type and providing the source and target connector details.
Upon successful submission, DCT displays a confirmation notification. For example, "Hyperscale Job enabled and started successfully" and the job status changes to Pending in the Compliance Jobs list.
Execution behavior
When a Hyperscale execution is triggered, DCT performs the following steps:
1. Global sync — Global objects are synchronized from DCT to each Compliance Engine associated with the job.
2. Export — Compliance job artifacts (rule set, connectors, algorithms) are exported from DCT as a sync bundle.
3. Upload — The sync bundle is pushed to the registered Hyperscale orchestrator.
4. Import — Objects are imported into the Hyperscale orchestrator along with connector credentials.
5. Parallel execution — Masking runs across multiple Compliance Engines in the Hyperscale cluster. Tables are split into chunks and processed concurrently.
What's next