Settings for Enabling and Configuring Incremental Builds
Use these settings to turn on incremental builds, specify the maximum allowed duration of an incremental build per aggregate, and specify the maximum number of partitions per aggregate.
Your user ID must be a super user to modify these settings.
Settings
AGGREGATE.INCREMENTALUPDATE.ENABLED
Set to True to use incremental builds for all of the aggregates for a cube when the fact dataset uses an incremental indicator. Full builds are still done for user-defined aggregates that are joins or unions of two or more fact tables.
AGGREGATE.INCREMENTALUPDATE.ALLPARTITIONMATERIALIZATIONS.DURATION
Specify the maximum length of time to allow for an incremental build of an aggregate table.
AGGREGATE.INCREMENTALUPDATE.MAXCONSECUTIVESTATICPARTITIONS
Specify the maximum number of partitions to allow for each incrementally built aggregate. When this threshold is exceeded, the partitions are consolidated. Lower values relative to the default result in slower consolidations and faster queries. Higher values result in faster consolidation and slower queries.
aggregate.batch.gracePeriodOverrides.enabled
Enables incremental builds to be triggered via API. Requires aggregate.batch.cube.gracePeriodOverrides.enabled to be enabled on the cubes you want to run incremental builds for. For more information, see Rebuilding Aggregates Using the REST API.
The default value of this setting is False. You do not need to restart the engine after changing it.
Enabling this functionality can potentially cause your system to become strained by expensive aggregate rebuilds.