About

Scheduling builds of prediction-defined and user-defined aggregates can be configured per cube. A cube can either have one or more scheduled builds, or would build aggregates immediately after prediction. You can use scheduling as follows:

1. Enable the scheduling settings on cube or engine level.
2. Create schedules.
3. Monitor aggregate builds.

For more information about each step, see the sections below.

Enabling schedules

To enable scheduling for individual cubes, follow the procedure in Cube Level Configuration Settings to enable the following settings:

• aggregates.new.build.scheduled: When true, new aggregate instance builds are postponed until the next scheduled batch build. If false (default), new aggregate instances may be queued for building at any time.
• aggregates.uda.build.scheduled: When false (default), new user-defined aggregate build instances are queued for building following the project publish event. If true, UDA builds are postponed until the next scheduled batch build.
• aggregates.predictionDefined.build.scheduled: When false (default), new prediction-defined aggregate build instances are queued for building following the project publish event. If true, PDA builds are postponed until the next scheduled batch build.

In case you need scheduling to be enabled for all projects, follow the procedure in Changing Engine Settings to enable the settings above (no restart required).

Managing schedules

When scheduling is enabled, you can view and manage schedules using AtScale's REST API. For details about the available endpoints and parameters, see Aggregate Creation Schedule.

Viewing results

When an aggregate definition or instance is scheduled, its status is Pending. You can view this in the aggregates monitor, for details see Monitoring Aggregate Usage.

More information

Aggregate creation can be scheduled so that it reduces data warehouse costs. For details, see Avoiding costs during downtime