Aggregate Incremental Builds Settings
You can use the following settings to configure incremental aggregate builds at the model level.
-
aggregate.incrementalUpdate.enabled
: Set to True (default) to use incremental builds for all of the aggregates for a model 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 tables. -
aggregate.incrementalUpdate.indicatorLookup.addPreviousMaxConstraint
: Whether or not to use the previous MAX value of the indicator as a constraint to improve performance. The default value is True. -
aggregate.incrementalUpdate.indicatorLookup.duration
: Maximum time allowed to lookup incremental indicator. The default value is 30 minutes. -
aggregate.incrementalUpdate.indicatorLookup.reusePerBatch
: Whether or not to use the same max indicator lookup per batch per indicator to improve performance. The default value is True. -
aggregate.incrementalUpdates.immutable.enabled
: Set to True (default) to enable incremental builds of aggregates that use joins on rarely changing dimensions. -
aggregate.incrementalUpdates.semiAdditive.enabled
: Set to True to enable support for incremental updates on semi-additive metrics. The default value is False. -
aggregate.batch.cube.gracePeriodOverrides.enabled
: Enables incremental builds for the model to be triggered via API. Requires theaggregate.batch.gracePeriodOverrides.enabled
global setting to be enabled. For more information, see Rebuilding Aggregates Using the REST API.The default value of this setting is
False
.ImportantEnabling this functionality can potentially cause your system to become strained by expensive aggregate rebuilds.